Posts by mewbysea

1)

Message boards : Number crunching : Exceeded CPU time quota.

( Message 4416 )
Posted 3241 days ago by mewbysea
If this is the same problem, can you do a server-abort (if that's the right term) to recall these units that may still be queued but not yet started?
2)

Message boards : Number crunching : Checkpointing

( Message 4147 )
Posted 3326 days ago by mewbysea
Running much closer to the estimates this time, and pausing and resuming as expected.

This 1abe wu estimated at about 1hr52min, completed in about 1hr45min.

This 1tng wu estimated at about 2hr3min and hit almost on the nose.

Running Q6600 2.4 GHz with Vista for both.
3)

Message boards : Number crunching : Checkpointing

( Message 4139 )
Posted 3329 days ago by mewbysea
I had at least two wu's in the last batch that successfully paused to allow other projects in BOINC to crunch and then resumed to finish. Both had an initial estimated work time of about 7hrs20min, and actually completed in about 2 hours. Pause was at about 1hr40min.

See wu 3394 and wu 4034 for details.
4)

Message boards : Number crunching : Checkpointing

( Message 4100 )
Posted 3333 days ago by mewbysea
I had several that ran smoothly start to finish, but no indication they ever had to pause and get out of the way for another project. Sorry, I never got a chance to "catch them in the act" and force a pause.
5)

Message boards : Number crunching : with few other projects?

( Message 4075 )
Posted 3341 days ago by mewbysea
hi all,
Some workunits sent over during the weekend had the estimated time lower than it should have been. It resulted in many clients ending up with 'compute error'. I underestimated the CPU time needed for the workunit.

Later I sent workunits with increased CPU time estimate and most of them ran successfully. Did anyone who got the 'compute error' get successful completion of these workunits ?

Thanks,
Arun


This may not be your revised version, but I got some that finally were able to at least claim their computer time and credit, but they also errored out with the same exit code. They did have the de-bugger run though so that may be of use. See result ID 8044 for an example. The BOINC Manager message for this one, which ran for about 1:20:00 with about 8 projects sharing 3 cpu cores, had the same message as the zero credit claimed wu's (which also ran for about that long):

6/14/2008 5:53:33 PM|Docking@Home|Aborting task 1tng_mod0011sc_50_467992_6: exceeded CPU time limit 4288.403915
6)

Message boards : Team Invites and Sigs : Team-SciFi pulls up to the dock

( Message 3053 )
Posted 3769 days ago by mewbysea
Hi folks! Team Sci-Fi has been working on Docking@Home for a while, but our members have now decided to put some increased effort here.

Check us out here , visit the forums, or watch us throughout the BOINC-verse. Visitors and new members are welcome!