Seti@Home optimized science apps and information
Optimized Seti@Home apps => Linux => Topic started by: codeman05 on 30 Apr 2009, 08:52:30 pm
-
Hey guys,
System is a Q6600 @ 3.0GHz running Debian x86.
I just switched one of my headless linux boxes over to AP using boinc 6.6.20 and the linux SSE3 AP application shown on the homepage.
I'm crunching my first AP units as we speak...but I'm impatient ;) and was wondering what you guys would expect the time frame for an average AP unit to complete on a rig similar to mine with this ap.
BOINC is currently estimating 35 hours (I was thinking something closer to 15hrs), but since I'm only a few percent into it I'm sure that is probably ncorrect
Thanks for all the work on this app!
-
Hey guys,
System is a Q6600 @ 3.0GHz running Debian x86.
I just switched one of my headless linux boxes over to AP using boinc 6.6.20 and the linux SSE3 AP application shown on the homepage.
I'm crunching my first AP units as we speak...but I'm impatient ;) and was wondering what you guys would expect the time frame for an average AP unit to complete on a rig similar to mine with this ap.
BOINC is currently estimating 35 hours (I was thinking something closer to 15hrs), but since I'm only a few percent into it I'm sure that is probably ncorrect
Thanks for all the work on this app!
I'd agree with the 15 hour estimate. What you're probably seeing is the Duration Correction Factor causing an over estimate.
The Astropulse progress is quite linear, though there's a small sawtooth effect in 5.03 builds. Divide the time used so far by the fraction done to get a better full runtime estimate than BOINC will be able to provide.
The optimized code has a feature which can make the runtime even shorter for some AP WUs, once the limit of 30 repetitive pulses is reached the search code for those is bypassed. More often than not if that happens at all it is quite early but it can be later, the progress rate inflects upward whenever it happens.
Joe