Checkpointing, more credits? Or more models?

Message boards : Number crunching : Checkpointing, more credits? Or more models?

To post messages, you must log in.

AuthorMessage
Profile feet1st

Send message
Joined: 7 Mar 06
Posts: 313
Credit: 116,623
RAC: 0
Message 1455 - Posted: 2 May 2006, 2:48:12 UTC

At one point it was mentioned that we were seeing 3x productivity on clients with the new checkpointing. I haven't tracked things closely enough... when I lose work due to preemption, does the time spent reset back to the checkpoint? And the credits is based on time spent, right?

Or if time spent always rolls forward, then we'd just see more model completions per hour of time? (because less time is spent retracing the steps we had made prior to preemption).
ID: 1455 · Report as offensive    Reply Quote
Profile feet1st

Send message
Joined: 7 Mar 06
Posts: 313
Credit: 116,623
RAC: 0
Message 1458 - Posted: 2 May 2006, 14:26:14 UTC - in response to Message 1456.  



IF the Work Unit is removed from memory, it will always roll back to the last checkpoint. When it starts on my systems this will usually result in lost time as well. The clock does not keep rolling forward if the percent resets. This is why it is still a good idea to set keep in memory to yes.

All the project loose somme time because of this loss. CPDN and Rosetta are two of the more lossy in this regard, but all projects loose some time this way.


...so, on average, with the enhanced checkpointing, we should expect to see a credit increase throughout the project, along with increased project TFLOPS (which as you've pointed out elsewhere appear directly calculated from credits issued).
ID: 1458 · Report as offensive    Reply Quote

Message boards : Number crunching : Checkpointing, more credits? Or more models?



©2024 University of Washington
http://www.bakerlab.org