On Sat, 28 Mar 2020 at 10:25, Ralph Corderoy <[email protected]> wrote:
> > Unfortunately, that machine seems to be stuck waiting for the > > server(s) to let it download anything. I presume they are prioritising > > higher-specification machines. > > Maybe. One snippet of #dorset says > > > folding@home ran out of work for me. I resumed boinc telling it to > > only work when idle (f@h runs regardless when there's folding to > > be done) > > That's one nice thing about WCG, you can set it to only do the > project/s you want, but to give you work for any others if they > don't have any. I'm not sure if BOINC its self can do that. > > I don't use any of them so have no insight. > (The 'I resumed boinc' was me) I've not seen rosetta@home waiting for work units yet so I'm not sure what would cause it. Although, I'm only running it when folding@home is idle. I only have a single fairly low powered dual-CPU (Turion) machine spare to use, which I notice comes very far down this list: https://boinc.bakerlab.org/rosetta/cpu_list.php Nice article here, folding@home the main focus, which mentions back-offs when requesting new work: https://www.extremetech.com/computing/308332-foldinghome-crushes-exascale-barrier-now-faster-than-dozens-of-supercomputers The Folding@home project definitely seems better at publicity. :-) Also WCG is World Community Grid, not currently researching COVID-19 specifically: https://www.worldcommunitygrid.org/research/viewAllProjects.do Tim. */ -- Next meeting: BEC, Bournemouth, Tuesday, post-lurgi 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:[email protected]
