i'm new here, i got a dual core intel 2.66GHz [Family 6 Model 15 Stepping 6] processors. i just ran the work unit # 255014325 called de_separation_10_3s_fix_5_1610326_1300391361_0. i don't have a double precision gpu, otherwise i would use it. i'm running on pure cpu power here.

my goodness it seemed this work unit kicked my rigs ass. the last couple of work units got crunched relatively quickly. but the initial "to completion" time for this work unit was 4 hours, but it ended up taking over 11 hours. and then it returned "verified but no consensus yet". are many of these work units suited to work with double precision gpu's? or are these computations very complex and take hours to accomplish? it seemed like as i was watching the "to completion" time, it kept increasing, not decreasing. i already tell boinc to use 100% of my cpus and 85 to 90% cpu time. i know the computer's working because i monitor the temperature carefully (i don't wanna burn my rig out running these programs). opinions anyone?

... before i inquire upon how it is possible to choose the name admin for a username on a forum, allow me to answer your question.

I am not entirely aware of how long seperation WU's run on my CPU, but nbody applications (the one you stated is a sepeation WU) run at ~1 hour in my Phenom II x2 550 @ 3.5 ghz.

As for your *moving completion time*, from my experience, initial runs base their estimated time of completion on your BOINC CPU benchmark(automatically done by BOINC). After your first WU however, subsequent WU's downloaded and worked on base their estimated time of completion upon the completion time of the most recent WU submitted to the server.

for example, if your WU took 12 hours to complete, the next WU's estimated time of completion will be around 12 hours. if that WU finishes in 11, the next WU downloaded will have an estimated time of 11 hours, and so on.



Simply put, estimations are based upon the BOINC client, and the application itself. there isn't anything wrong with your CPU, as your clock time nearly matches your CPU time (think of CPU time as a measure of CPU efficacy using the amount of time the CPU utilized 100% of it's resources verses the actual time elapsed) Thus, your CPU has no issue regarding performance.

by the way, the WU saying result inconclusive just means that it's waiting for another host to submit the same WU to compare to, to check for validity of data. It's basically like waiting for validation.