So I installed BOINC and then started running rosetta through it. Things were working fine running off normal specs. So then I decided to configure for less CPU usage and set it at around 50%. Then things stopped running completely, even after i restart the client or drop then readd rosetta. Whats the deal?

What happens if you temporarily go back to running 100%? Does it start up like normal? And then try switching back to 50%. So, is this reproducible?

What version of BOINC are you using? This used to be a problem around 5.7.? (I don't remember what version the bug got fixed in, but I was the one who reported the problem initially).

I saw on the Rosetta forums last night that WUs mysteriously stopping seems to be a new bug introduced with the last update of the science app. Most reports (if I'm remembering right) were on Macs. So what OS are you using?

What happens if you temporarily attach to another project? Do you see the same behavior.

I'm trying to narrow it down to a problem with Rosetta or a problem with the core client.

---

Kathryn :o)

What happens if you temporarily go back to running 100%? Does it start up like normal? And then try switching back to 50%. So, is this reproducible?

What version of BOINC are you using? This used to be a problem around 5.7.? (I don't remember what version the bug got fixed in, but I was the one who reported the problem initially).

I saw on the Rosetta forums last night that WUs mysteriously stopping seems to be a new bug introduced with the last update of the science app. Most reports (if I'm remembering right) were on Macs. So what OS are you using?

What happens if you temporarily attach to another project? Do you see the same behavior.

I'm trying to narrow it down to a problem with Rosetta or a problem with the core client.

I have a Mac OS 10.4.9 dual 2 GHz PPC G5 with 2.512 GB DDR SDRAM running Boinc v 5.8.15. I run at full 100% cpu all the time but have recently had Rosetta tasks that hang. They generally will not start again even by 'suspending' the taks and 'resuming' the task. I have shut down Boinc and restarted Boinc which will usually correct this kind of a problem. This past two days the tasks stay in memory but doing no work and the only way to get going is to Abort the task. Boinc reports the jobs are running when they are not.

I post this to help address the last question you have. I have other tasks from other Projects running and they are still operational except when Rosetta tasks stop, Boinc considers them running and will not allow another task to start. I have seen holds like this up to 10 hours in the past few days.

Hope this comment helps you.

Yup.

I do believe it's the same problem other people are experiencing at Rosetta.

My best advice is to check out Number Crunching there (probably the "Problems with Rosetta version 5.54" thread). And see if any of the project staff have addressed the issue.

I haven't check the boards since last night, so I'm not sure if there's been any sort or response.

---

Kathryn :o)

What happens if you temporarily go back to running 100%? Does it start up like normal? And then try switching back to 50%. So, is this reproducible?

What version of BOINC are you using? This used to be a problem around 5.7.? (I don't remember what version the bug got fixed in, but I was the one who reported the problem initially).

I saw on the Rosetta forums last night that WUs mysteriously stopping seems to be a new bug introduced with the last update of the science app. Most reports (if I'm remembering right) were on Macs. So what OS are you using?

What happens if you temporarily attach to another project? Do you see the same behavior.

I'm trying to narrow it down to a problem with Rosetta or a problem with the core client.

I have a Mac OS 10.4.9 dual 2 GHz PPC G5 with 2.512 GB DDR SDRAM running Boinc v 5.8.15. I run at full 100% cpu all the time but have recently had Rosetta tasks that hang. They generally will not start again even by 'suspending' the taks and 'resuming' the task. I have shut down Boinc and restarted Boinc which will usually correct this kind of a problem. This past two days the tasks stay in memory but doing no work and the only way to get going is to Abort the task. Boinc reports the jobs are running when they are not.

I post this to help address the last question you have. I have other tasks from other Projects running and they are still operational except when Rosetta tasks stop, Boinc considers them running and will not allow another task to start. I have seen holds like this up to 10 hours in the past few days.

Hope this comment helps you.

Im running 5.8.15 of boinc on OSX. I went and tried to see if i could get protiens@home running, no dice. Its a seporate error though, I cant even get connected to them. Im running into some random program shutdowns too.

I think ill try reinstalling the whole 9 to see if it does anything.

So I installed BOINC and then started running rosetta through it. Things were working fine running off normal specs. So then I decided to configure for less CPU usage and set it at around 50%. Then things stopped running completely, even after i restart the client or drop then readd rosetta. Whats the deal?

Hi G,

When you set any given project to run at 50% CPU usage, it doesn't mean that your computer will run all the time using only half of your CPU. It means it will balance the usage time so the project will run about half of that time. If your machine runs an average of 6h/day, BOINC will try to schedule your CPU so it runs in 3 of those 6h. HTH,

Regards,
Wander

Wander,

That's a good point. I assumed by CPU usage he was referring to the CPU throttling feature released in the 5.8.x line.

But it is possible that he could be talking about Resource Share.

G...


Could you clarify for me which it is?

---

Kathryn :o)