spicedog
with my newfound hyperthreading, i mostly run seti@home and other processor intensive applications... but it seems slow at times. From what I
read around a 3GHz should be able to do a seti packet in around 90 minutes, but mine takes 2.5 hours consistnently. Any cpu program I run on it says it's a real 3ghz cpu. Any thoughts?
read around a 3GHz should be able to do a seti packet in around 90 minutes, but mine takes 2.5 hours consistnently. Any cpu program I run on it says it's a real 3ghz cpu. Any thoughts?
Participate on our website and join the conversation
You have already an account on our website? Use the link below to login.
Login
Create a new user account. Registration is free and takes only a few seconds.
Register
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Reign_Of_Chaos
you using the full Screensaver type Seti@Home or the Faster more Compact CommandLine Version? the CLV does complete a packet in about 90Mins on my 3.0 system. try ftp://alien.ssl.berkeley.edu/pub/setiatho...nnt-cmdline.exe
even though it says i386-winnt... it runs awesome on my P4 3.0 win WinXP. Hope that helps
even though it says i386-winnt... it runs awesome on my P4 3.0 win WinXP. Hope that helps
KillerKebab
Windows XP comes from NT though so that would be it :P
