I think Eponymous is on track. SetiQ doesn't really take into account programs like SetiDriver that 'stock up' on WU's
take this example:
Average Time 2 days 19 hr 28 min
Average CPU Time 8 hr 31 min (12% efficient)
This is a machine running 24/7 with a cache of 8 WU. By the time a WU is crunched and returned, SetiQ has had to wait for 7 other WU's to process.
8 x 8.5 hrs = 2 days, 19.5 hours (roughly)
Well, the more I think about it, the more I think efficiency is not a good way to describe it. I mean, If I'm running Photoshop or some Video edititng stuff, the WU's take much longer to process. I can end up with a 10 hour WU (using the above example).
CPU time only represents how long the PC took to process the WU, not what else the processor was doing.
It's too late and this really doesn't matter (to me). The fleet is on cruise control, and so am I.
out!