1)
Message boards :
Number crunching :
Problems and Technical Issues with Rosetta@home
(Message 97606)
Posted 25 Jun 2020 by 2fifty6 Post: I run Milkyway, where the tasks take one minute on a graphics card. I can't download them that often, the server doesn't allow it. I only set my cache to 3+3 hours though. For example, on my CPUs I currently have 66 CPU tasks running and 12 tasks queued. It doesn't seem right to me to be constantly downloading 1 task at a time, I'm sure the server prefers I download batches of say 6. In fact on my 24 core machines, they could be trying to get tasks from Rosetta extremely often if they got one at a time. What if one task finished at 3:00pm, so it downloaded a new task, then another core finished at 3:01pm? And another at 3:02pm? I suspect I'd hit a server limit of how often I can contact.Ok, that sounds like a reasonable fringe case. But for the vast majority of people whose computers take hours to run each WU, it doesn't seem like a cache of jobs really adds much benefit from a project standpoint. It just unnecessarily delays WU completion as they sit claimed-but-idle in someone's queue. |
2)
Message boards :
Number crunching :
Problems and Technical Issues with Rosetta@home
(Message 97602)
Posted 25 Jun 2020 by 2fifty6 Post:
In this era of high speed, always-on internet connections, what purpose does the cache even serve? I have mine set to zero so it just downloads WUs as others finish and it works just fine. And since those WUs are always "fresh," I never have to worry about running up against the deadline. |
©2023 University of Washington
https://www.bakerlab.org