From: Travis Desell <[email protected]> > Getting rid of the entries with negative variance seemed to fix the WUs getting > immediately timed out (at least on DNA@Home), but on milkyway@home it > looks like the problem is still happening on the GPU applications....
Are the milkyway@home GPU applications the type where the CPU part first stays busy a while loading the GPU part into graphics memory, then goes into an almost idle mode for most of the rest of the workunit where it does little except checking whether the GPU part says it's finished, then finally goes into a mode where stats busy unloading the outputs from graphics memory? If so, I'd expect some large changes in any speed calculations that don't restrict the CPU operations observed to just one of those modes. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
