Alterego,
Looks at the date/time of your last work unit – it's been a while, eh?!? ;-)
If you have any doubt, take a look at my username at http://vspx27.stanford.edu/cgi-bin/main.py?qtype=userpage&username=powder2glass – note that 50-day CPU count is 61 and 7-day count is 5 (!) ... with last unit completed 3 days ago (a slow straggler).
Phillip didn't mention the "official" Google Group for Compute where a buncha of people are discussing the problem – see http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&c2coff=1&group=google.public.labs.compute
This is definately a "chink in their armor" IMHO ...
alek |
It takes my 1.7 Ghz laptop quite a while to finish a work unit. 8 days really isn't out of line especially considering I've been using it a lot. I'll check out the group. |
Take a look at your "percent done" on the toolbar – once you hit 100%, it will just stay there ... or at least until Google fixes things ... so you'll be in the same boat as a couple of hundred thousand other folks! :-( |
I don't use the toolbar. I have GoogleDCC in my startup folder. |
The "dam" may have broken this morning as it looks like machines are picking up new work units and starting processing – assuming not another hiccup (still no official word from Google what the problem was), the following URL that tracks my team's daily progress (with 60 CPU's) should start showing some progress as these new work units are completed:
http://www.powder2glass.com/Google_Toolbar_Compute/stats.html |
