I suppose most people have noticed this, and it's probably been discussed, but maybe some newer seti users will benefit.
I have been running seti on a newer Dell 8100 with the fancy 866m p3. This has 512k instead of 256k and runs at 133 with some data prefetch etc etc. Point is, it should be a pretty quick machine for seti.
It was turning in a wu in 22 to 26 hours.
That's not 'pretty quick' for this processor.
I turned off Kazaa and Norton, so I am not sure which was the culprit, but anyway, times are typically less than 6 hours now. That's even a little faster than I hoped for.
Anyway, if anyone is getting discouraged because they can't rack up wu's as fast as they think they should, maybe some TSR's are slowing you down, it might be worth a look.
I have been running seti on a newer Dell 8100 with the fancy 866m p3. This has 512k instead of 256k and runs at 133 with some data prefetch etc etc. Point is, it should be a pretty quick machine for seti.
It was turning in a wu in 22 to 26 hours.
That's not 'pretty quick' for this processor.
I turned off Kazaa and Norton, so I am not sure which was the culprit, but anyway, times are typically less than 6 hours now. That's even a little faster than I hoped for.
Anyway, if anyone is getting discouraged because they can't rack up wu's as fast as they think they should, maybe some TSR's are slowing you down, it might be worth a look.