Hey guys,
I installed this last night and the cpu time has been over 7 hours to get to around 18%. Is that normal? I think it's going a little slow. :eek:
Thanks!
Printable View
Hey guys,
I installed this last night and the cpu time has been over 7 hours to get to around 18%. Is that normal? I think it's going a little slow. :eek:
Thanks!
are you using the command line version or the GUI version from the berkley site? (the GUI version takes a lot longer.)Quote:
Originally posted by gateways_rule
Hey guys,
I installed this last night and the cpu time has been over 7 hours to get to around 18%. Is that normal? I think it's going a little slow. :eek:
Thanks!
I used to have the SETI@home Graphic version, and i could finish a whole packet in 7 hours...
The GUI Version from the Berkely site. It looks like this:
http://gatewaysrule.netfirms.com/seti.JPG
lol.. ya thats a little slow.. since you just started, ditch the GUI and go get the cmd-line version. You should be doing a workload in under 10 hours with your CPU. But make sure you dont do any CPU intense things (ie gaming) while running SETI or that will slow it down also.
Shadowfire.. yours happens to be low also. Yours should be done in about 4 hours. If your running the GUI then you should switch also.
Here are some of my results...
C400@500 12-13 hours
Athlon 950 ~6 hours
Tbird 1.4 ~4.5 hours
slydog
My Xeon 1.7 dual proc system does 2 WUs in approximately 4 hours. That is one per proc per 4 hours. I use the command line Seti version. Your performance should be similar depending on your proc speed.