Posts by Rick Spies

1) Message boards : Number crunching : Newbie Q&A, if you're new, have a view! (Message 68683)
Posted 22 Nov 2010 by Rick Spies
Post:
Well, the discussion has been carried about many times before. All I can really say is that Rosetta is giving your CPU work when your machine is asking for it. The amount of work requested, and when it is requested is entirely up to the BOINC core client running on your machine, and the code that decides how and when to fetch work, and how to handle two projects when one is down is an area that is changing frequently. They are still really trying to achieve the right balances between enforcing your resource shares, always having enough work for all of the CPUs you've configured for BOINC to use, returning work on time (i.e. before deadlines), etc....


Thanks for your helpful explanation. It's good to know R@h is always there with more work; I'll stop fretting.

10 days of work is my habit because the SETI@home project is very unreliable and not always available. It goes down perhaps once each month, or currently, more than one month as they replace and rebuild a crashed server. S@h also shuts-down Tue-Thu every week. I guess that's the best they can do on a near-zero budget. I believe the majority of their money comes from donors like me.

I started R@h to fill-in these downtimes.
2) Message boards : Number crunching : Newbie Q&A, if you're new, have a view! (Message 68677)
Posted 21 Nov 2010 by Rick Spies
Post:
R@h does not have GPU tasks. The only time shown in your messages that CPU work was requested, you received some. How are your network settings configured? How often is BOINC to connect and how many additional days of work are you asking it to keep on-board?


The GPU messages are something quirky about my BOINC installation. They appear even though I've got "Use GPU..." turned-off. This has not been a problem for either SETI@h or R@h. SETI@h can use nVidia GPUs; I have an ATI anyway.

My BOINC network configuration is completely unrestricted; it can do whatever it wants, whenever it wants, etc....

I ask for 10 days of work, my norm from participating on SETI@home, which goes down often. (It's been down for ~3 weeks right now.)

My last two R@h work units are being crunched now. Since it takes ~30 hours to crunch one work unit, these are almost certainly the same WUs I was running yesterday. (This PC is off a night.) In 15.5 hours, I'll have no work.

Today's log:
11/20/2010 10:18:57 AM rosetta@home Sending scheduler request: To fetch work.
11/20/2010 10:18:57 AM rosetta@home Requesting new tasks for GPU
11/20/2010 10:18:58 AM rosetta@home Scheduler request completed: got 0 new tasks
11/20/2010 10:51:30 AM rosetta@home Computation for task Ross2X3_SAVE_ALL_OUT_r435_005_22542_1381_0 finished
11/20/2010 10:51:30 AM rosetta@home Starting 1ZGG_R2_LESSPCSCST2_BOINC_abrelax.default.v1_SAVE_ALL_OUT_22545_19922_0
11/20/2010 10:51:32 AM rosetta@home Starting task 1ZGG_R2_LESSPCSCST2_BOINC_abrelax.default.v1_SAVE_ALL_OUT_22545_19922_0 using minirosetta version 217
11/20/2010 10:51:33 AM rosetta@home Started upload of Ross2X3_SAVE_ALL_OUT_r435_005_22542_1381_0_0
11/20/2010 10:51:37 AM rosetta@home Finished upload of Ross2X3_SAVE_ALL_OUT_r435_005_22542_1381_0_0
11/20/2010 10:51:38 AM rosetta@home Sending scheduler request: To report completed tasks.
11/20/2010 10:51:38 AM rosetta@home Reporting 1 completed tasks, requesting new tasks for GPU
11/20/2010 10:51:39 AM rosetta@home Scheduler request completed: got 0 new tasks
11/20/2010 11:15:11 AM rosetta@home Computation for task thioredoxin_LESSPCSCST_BOINC_abrelax.default.v1_SAVE_ALL_OUT_22535_3544_0 finished
11/20/2010 11:15:13 AM rosetta@home Started upload of thioredoxin_LESSPCSCST_BOINC_abrelax.default.v1_SAVE_ALL_OUT_22535_3544_0_0
11/20/2010 11:15:17 AM rosetta@home Finished upload of thioredoxin_LESSPCSCST_BOINC_abrelax.default.v1_SAVE_ALL_OUT_22535_3544_0_0
11/20/2010 11:15:22 AM rosetta@home Sending scheduler request: To report completed tasks.
11/20/2010 11:15:22 AM rosetta@home Reporting 1 completed tasks, requesting new tasks for CPU and GPU
11/20/2010 11:15:24 AM rosetta@home Scheduler request completed: got 1 new tasks
11/20/2010 11:15:26 AM rosetta@home Started download of 1T17_pcs_cst_files.r2.pnoe.v1.zip
11/20/2010 11:15:33 AM rosetta@home Finished download of 1T17_pcs_cst_files.r2.pnoe.v1.zip
11/20/2010 11:15:33 AM rosetta@home Starting 1T17_R2_pNOE_LESSPCSCST2_BOINC_abrelax.default.v1_SAVE_ALL_OUT_22550_20557_0
11/20/2010 11:15:34 AM rosetta@home Starting task 1T17_R2_pNOE_LESSPCSCST2_BOINC_abrelax.default.v1_SAVE_ALL_OUT_22550_20557_0 using minirosetta version 217
11/20/2010 9:36:38 PM rosetta@home Sending scheduler request: To fetch work.
11/20/2010 9:36:38 PM rosetta@home Requesting new tasks for GPU
11/20/2010 9:36:39 PM rosetta@home Scheduler request completed: got 0 new tasks
3) Message boards : Number crunching : Newbie Q&A, if you're new, have a view! (Message 68670)
Posted 20 Nov 2010 by Rick Spies
Post:
I'm pretty new to Rosetta (but have been on SETI@home for >10 years).

Everything has been working just fine, but it's been many days since I last received work. I'm about to run out of work units, with two in process now and only one more to replace them when completed. I do want to keep my CPUs busy. The Home Page makes it look like there are plenty of jobs available.

Any ideas? Below is today's messages so far:

11/19/2010 6:21:40 AM rosetta@home Restarting task Ross2X3_SAVE_ALL_OUT_r435_005_22542_1381_0 using minirosetta version 217
11/19/2010 6:21:43 AM rosetta@home Restarting task thioredoxin_LESSPCSCST_BOINC_abrelax.default.v1_SAVE_ALL_OUT_22535_3544_0 using minirosetta version 217
11/19/2010 6:21:44 AM rosetta@home Sending scheduler request: To fetch work.
11/19/2010 6:21:44 AM rosetta@home Requesting new tasks for GPU
11/19/2010 6:21:46 AM rosetta@home Scheduler request completed: got 0 new tasks
11/19/2010 12:58:34 PM rosetta@home Sending scheduler request: To fetch work.
11/19/2010 12:58:34 PM rosetta@home Requesting new tasks for CPU
11/19/2010 12:58:35 PM rosetta@home Scheduler request completed: got 1 new tasks
11/19/2010 12:58:37 PM rosetta@home Started download of 1ZGG_pcs_cst_files.r2.v1.zip
11/19/2010 12:58:43 PM rosetta@home Finished download of 1ZGG_pcs_cst_files.r2.v1.zip
11/19/2010 1:42:37 PM rosetta@home Sending scheduler request: To fetch work.
11/19/2010 1:42:37 PM rosetta@home Requesting new tasks for GPU
11/19/2010 1:42:39 PM rosetta@home Scheduler request completed: got 0 new tasks


Thanks,
Rick
4) Message boards : Number crunching : New WUs being started before older ones are done (Message 68335)
Posted 2 Nov 2010 by Rick Spies
Post:
Rick, I hear people report such things every once and a while, but it's not all that common. I would hope they would run in expiration order as well. What BOINC Manager version are you running? It is really the BOINC Manager that decides which tasks to schedule when, not the Rosetta application. Perhaps there is a fix in a newer version.


I'm running BOINC v6.10.58, which is the most recent version. To be a bit more complete, I'm running Win7 x64 on an Intel Core2Duo proc. This has been a problem since I started Rosetta in August. It's not a problem with SETI@home.

If there is anything I can do to help you troubleshoot this problem, just ask.
5) Message boards : Number crunching : New WUs being started before older ones are done (Message 68326)
Posted 1 Nov 2010 by Rick Spies
Post:
I pretty new to Rosetta (but have been on the SETI project for >10 years). I am using a dual core PC for Rosetta.

I've noticed that Rosetta will start a new pair of WUs before finishing other WUs.

For example, right now I have six WUs in various stages of completion:

27%
21%

11%
10%

9%
5%

Rosetta always works on them in pairs, as shown above, switching from one to another or starting a new pair at any time.

QUESTION:
Is it normal for Rosetta to begin new work units before completing others? This does not happen on SETI.

Looking at my WUs, I can see this work shifting is jeopardizing completion of partially-processed WUs before their reporting deadlines, wasting a lot of time and CPU cycles. WUs are not being worked on in report deadline order either.

Any insight would be appreciated.

Rick
Portland, OR






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