Advanced search

Message boards : Number Crunching : Low credit workunit

Author Message
Profile Skivelitis2
Avatar
Send message
Joined: 16 May 15
Posts: 60
Combined Credit: 11,066,329
DNA@Home: 19,068
SubsetSum@Home: 575,552
Wildlife@Home: 10,471,708
Wildlife@Home Watched: 9,158s
Wildlife@Home Events: 4
Climate Tweets: 391
Images Observed: 52

            
Message 6950 - Posted: 24 Apr 2017, 13:33:33 UTC

Host id: 50064

Work unit 1026227: 109,262.30 CPU seconds for 2003.44 credits
Work unit 1024941: 38,757.16 CPU seconds for 2006.08 credits

Most work is along the lines of the second work unit, the first seems to be some type of anomaly. Or am I missing something?

Travis Desell
Volunteer moderator
Project administrator
Project developer
Project scientist
Send message
Joined: 16 Jan 12
Posts: 1813
Combined Credit: 23,514,257
DNA@Home: 293,563
SubsetSum@Home: 349,212
Wildlife@Home: 22,871,482
Wildlife@Home Watched: 212,926s
Wildlife@Home Events: 51
Climate Tweets: 22
Images Observed: 774

              
Message 6979 - Posted: 29 Apr 2017, 15:30:16 UTC - in response to Message 6950.

Host id: 50064

Work unit 1026227: 109,262.30 CPU seconds for 2003.44 credits
Work unit 1024941: 38,757.16 CPU seconds for 2006.08 credits

Most work is along the lines of the second work unit, the first seems to be some type of anomaly. Or am I missing something?


Yeah these are the "monster" workunits being discussed in the news forum. I'm trying to figure out why on earth they're happening. I'm hoping the new application will get rid of them.


Post to thread

Message boards : Number Crunching : Low credit workunit