That stat is sorta misleading...
It's the total CPU time divided by the time that it took to get the WU back to SETIQueue...i.e.
You download about 10 WU's...They are timestamped. The client crunches them one at a time until it returns them all..
The last one returned may only take 4 hours to crunch, but you downloaded it (say) 2 days ago....so it would be 4 hours divided by 52 hours (2 days + the 4 hours crunching)....SETIDriver, because it stores WU's to be crunched, really squews these numbers because of the large time between when a WU is downloaded and when the result is uploaded...
