| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 21
|
|
| Author |
|
|
drghughes
Cruncher Joined: Jul 5, 2007 Post Count: 26 Status: Offline Project Badges:
|
I'm currently running a WU that is running for more than 3.5 hours between checkpoints (real time, though CPU time isn't that much less). I admit that my machine isn't the fastest, but even so, this is a long time.
Is this a one-off or is this the way that FAAH WU will run from now on? In which case my PC probably isn't suitable for FAAH any more. Thanks |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
That's a rather negative assumption. Is the job making progress in percent terms? Very occasionally there WAS a batch with only 1 or 2 checkpoints, a tough job thus, but not heard of any of those for a long time.
----------------------------------------If not making progress, but counting CPU time, suggest to restart BOINC. Sometimes a job hangs in a loop let us know edit: spelling corr.
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Mar 11, 2009 8:17:43 PM] |
||
|
|
drghughes
Cruncher Joined: Jul 5, 2007 Post Count: 26 Status: Offline Project Badges:
|
The WU is progressing without problems. I probably wouldn't have even noticed it except that I wanted to shutdown BOINC while I installed some software, went to BOINC Manager to watch for the next check point in the messages, and noticed that this WU hadn't checkpointed for a couple of hours. I left it alone and when it got to 50% done it wrote the checkpoint and BOINC moved on to the next project.
But if all FAAH WUs are going to run that long between checkpoints that's going to be a hassle. Let's say it's been running for 3 hours when I come to shutdown - I really don't want to be throwing away that much work. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Somewhere a few years ago I posted and maintained a table when FAAH was young. It showed the different checkpoint counts which in those days we could only find by observing the graphics... this is where the request grew to have a specific setting so it would print in the message log. There was even a request for a beep to tell volenteers when it was opportune to close, but as it is with duo/quad/octo, it would turn the crunch experience into a Stockhausen concerto.
----------------------------------------
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
drghughes
Cruncher Joined: Jul 5, 2007 Post Count: 26 Status: Offline Project Badges:
|
Somewhere a few years ago I posted and maintained a table when FAAH was young. It showed the different checkpoint counts which in those days we could only find by observing the graphics... this is where the request grew to have a specific setting so it would print in the message log. There was even a request for a beep to tell volenteers when it was opportune to close, but as it is with duo/quad/octo, it would turn the crunch experience into a Stockhausen concerto. Sekerob - I think that you've put this reply in the wrong thread. Do you know whether 3.5+ hours between checkpoints is normal for the current FAAH WUs? Thanks |
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges:
|
Can you please post the work unit you were working on so I can check something.
-Uplinger |
||
|
|
drghughes
Cruncher Joined: Jul 5, 2007 Post Count: 26 Status: Offline Project Badges:
|
|
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Somewhere a few years ago I posted and maintained a table when FAAH was young. It showed the different checkpoint counts which in those days we could only find by observing the graphics... this is where the request grew to have a specific setting so it would print in the message log. There was even a request for a beep to tell volenteers when it was opportune to close, but as it is with duo/quad/octo, it would turn the crunch experience into a Stockhausen concerto. Sekerob - I think that you've put this reply in the wrong thread. Do you know whether 3.5+ hours between checkpoints is normal for the current FAAH WUs? Thanks No, it's in the correct thread and before I did say that there were batches long time ago with just a few checkpoints. Anyway, please answer -Uplinger wanting to know the specific task number Added: Here's the link to the FAAH Checkpoint table http://www.worldcommunitygrid.org/forums/wcg/viewthread?thread=8331#70535 discussing a FAAH task stuck at 0%.
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Mar 11, 2009 9:01:26 PM] |
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges:
|
Thanks for the work unit information. I will investigate this work unit later.
Also, Sek is correct that we did have monster jobs at one point that would split into very few checkpoints per 8 hour run. Please be patient with me as we are working on lots of things at the moment. Thanks, -Uplinger |
||
|
|
JmBoullier
Former Community Advisor Normandy - France Joined: Jan 26, 2007 Post Count: 3716 Status: Offline Project Badges:
|
Do you know whether 3.5+ hours between checkpoints is normal for the current FAAH WUs? If you had said from the beginning how long a FAAH takes in general in this machine it would have been easier and faster to say if 3.5 hours between checkpoints is normal on this particular machine. You have not even said how long it has taken to reach this 50 % stage. Cheers. Jean. |
||
|
|
|