| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: GO Fight Against Malaria
Thread: GFAM: Checkpoint writing not adhering to client *Write to Disk* setting |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 13
|
|
| Author |
|
|
armstrdj
Former World Community Grid Tech Joined: Oct 21, 2004 Post Count: 695 Status: Offline Project Badges: 
|
We are currently testing a fix for the write to disk issue in our internal Alpha testing environment for both DSFL and GOFAM. If things go well there should be a beta soon.
Thanks, armstrdj |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thank you so much for the swift action, armstrdj.
Et al: Blame it on me ;P --//-- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Unthinking of me, re a tech comment on DSFL (uplinger ?) that the output file grows linearly with the number of jobs, if all the jobs output is required in a task and this *staging* structure of the app, hope this skipping of checkpoint writes is not going to loose the data i.e. that at the next write point all not yet written checkpoints get stored, 1K or 2K or 4K would not make a difference. I'd love to get the quick efficiency gain but have to accept then it's not feasible.
Looking forward to the positive word of programmer magic. --//-- |
||
|
|
|