Quote from: jjwhalen on March 23, 2010, 01:36:04 AMThe problem is the time is probably used most at the beginning and the end. Check the elapsed time the value () should be the cpu run time, the other value should be the wall clock time.Quote(Changed) CPU%: if CPU % < 1% add 1 digit, like 0.001 and round of properly. 0.000 should be shown as empty.
Sorry, but in v0.46 PrimeGrid's AP26 Search (cuda23) v1.01 is still showing no CPU activity (CPU % = null field, no CPU time in parentheses) through its entire run According to PrimeGrid's database, my most recent result reported an actual CPU time of 0.64sec on a run time of 628.64sec, or 0.102%. That's on an Intel Q9400 at 2.66GHZ, with an EVGA GTS250 moderately overclocked.
This still isn't a big deal for me, but I predict that as other projects optimize their CUDA (& possibly ATI) apps, you'll be seeing more tiny CPU:GPU ratios like this (depending, of course, on what kind of data they are crunching).
Best wishes.