Due to user feedback and an attempt to reduce the load on our servers, we increased the default target run time from 3 to 6 hours, increased job deadlines to 14 days, and added the target cpu runtime option of 2 days

Message boards : Technical News : Due to user feedback and an attempt to reduce the load on our servers, we increased the default target run time from 3 to 6 hours, increased job deadlines to 14 days, and added the target cpu runtime option of 2 days

To post messages, you must log in.

AuthorMessage
Admin
Project administrator

Send message
Joined: 1 Jul 05
Posts: 4668
Credit: 0
RAC: 0
Message 83087 - Posted: 14 Aug 2014, 0:00:00 UTC

Due to user feedback and an attempt to reduce the load on our servers, we increased the default target run time from 3 to 6 hours, increased job deadlines to 14 days, and added the target cpu runtime option of 2 days. Any input on this is appreciated, good or bad. Please post to this thread. We can revert to the previous values if necessary after assessing how these changes effect the project. Remember, you can always set the run time preference to your liking, from as low as 1 hr to as long as 2 days. It is the "Target CPU run time" option in the Rosetta@home specific preferences. Also keep in mind that it's a target run time but if the job is a large protein, it may take longer than 1 hour to generate 1 model so the actual run time can exceed the target run time (at least 1 model is generated).
ID: 83087 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
flobee

Send message
Joined: 28 Jan 19
Posts: 1
Credit: 201,161
RAC: 4,356
Message 90284 - Posted: 30 Jan 2019, 15:47:40 UTC - in response to Message 83087.  

hmm too bad. means people need to have 24/7 machines. i just tested rosetta the last few days and it gets now only 5% of resources.
Reasons:
- Too low deadlines (and my cpu time for you is for nothing when the time excceed the deadline? too bad! no, this is not the deal to offer free cpu time and the project dosnt make sense then)
- To much disk usage/ Smaller chuncks needed (not possible?)
Boinc gets ONLY 3-5GB diskspace. This means it blocks other jobs (like seti) beeing loaded even if 10/12 cores are iddle. they are block by diskspace until one of ~4 rosetta jobs is done to free diskspace.
- Note: Only once a day (for 1h) networking is activ. You should calculate how many jobs can be done during the next 24h but: Keep in mind that jobs can iddle for some few weeks because the cpu power is needed by owner. (seti seems to handle this with my setup/setting with enough time buffer to get the jobs done for sure.
ID: 90284 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
TuxNews

Send message
Joined: 21 Apr 19
Posts: 2
Credit: 1,956
RAC: 31
Message 90701 - Posted: 21 Apr 2019, 16:21:24 UTC

How to link World Community Grid? i changed account and points are lost...
ID: 90701 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote

Message boards : Technical News : Due to user feedback and an attempt to reduce the load on our servers, we increased the default target run time from 3 to 6 hours, increased job deadlines to 14 days, and added the target cpu runtime option of 2 days



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