This is concerning Rosetta on my laptop, running Vista. When any other projects are running, my CPU usage is in the 95-100% range. Recently, when Rosetta is running the CPU usage drops dramatically - yesterday it was down to 45-50%, and today it's under 10%. All my preferences are set to use 100% of processors. Any ideas why Rosetta is only using 10% instead of 100%?

Thanks in advance...

---

How many cores do you have?

---

How many cores do you have?

2

Right now, BOINC is running Rosetta on one core, and Seti on the other. CPU is up to 65%...

I had the same problem.

Pause the rosetta task, wait for a minute or two.

Restart the task.

It worked for me, I don't know if it will work for you.

The remaining time was going up instead of down. and it took 20 hours to do... 2%.

I had the same problem.

Pause the rosetta task, wait for a minute or two.

Restart the task.

It worked for me, I don't know if it will work for you.

The remaining time was going up instead of down. and it took 20 hours to do... 2%.

I tried it - as soon as I resume Rosetta, it drops back to 10%. And yes - the remaining time is going up. I've got one task running that is 50% complete in 9 hours - usually take 3 hours...

I aborted all Rosetta tasks in que, and the newly downloaded tasks (all mini 1.67) are utilizing 100%...

I had the same problem.

Pause the rosetta task, wait for a minute or two.

Restart the task.

It worked for me, I don't know if it will work for you.

The remaining time was going up instead of down. and it took 20 hours to do... 2%.

I tried it - as soon as I resume Rosetta, it drops back to 10%. And yes - the remaining time is going up. I've got one task running that is 50% complete in 9 hours - usually take 3 hours...

I aborted all Rosetta tasks in que, and the newly downloaded tasks (all mini 1.67) are utilizing 100%...

Hmmm, seems MIni 1.67 has it fixed.

Weird though, because I've never had a problem with Rosetta every since I joined... a WHILE ago.

---

The newly downloaded tasks ran properly for a while, and then went back to under-utilizing the cpu's (down to 10%), so I aborted them and the other projects are using 100%. Rosetta hasn't dowloaded any additional work...

Well... it seems it is a bug because I had 5 WUs doing that on my WINDOWS computer.
The one on Linux doesn't seem to do that.
I don't know if it has any relation.

For info the computer on Windows has:
3.2 GHZ with HyperThreading
1 Gig of Ram

The one on linux:
2.1 GHZ X2 core duo (and not CORE 2 DUO)
2 Gig of Ram

Let's wait for the programmers to fix this.

Let's wait for the programmers to fix this.

Well... running mini 1.71, and it's doing it again. The current wu has run 20 hours and completed 17% showing 32 hours remaining.

---

Starting at the beginning. Rosetta allows you to configure your runtime preference and then the client program tries to complete tasks in that timeframe. Having said that the highest preference allowed at present is 24hrs. So, something is still off.

The new 6.6 BOINC versions do not show CPU time on the task summary page. See my post. You have to select the specific task and look at the properties.

If Rosetta is only getting 10% of CPU, then the figures you have there would only be about 5 hours of actual CPU time. So what is limiting the CPU time available to BOINC? Could be other tasks running at higher priority then BOINC's low priority. Could be BOINC preferences to limit number of CPUs or % of CPU time.

---

Rosetta Moderator: Mod.Sense

Starting at the beginning. Rosetta allows you to configure your runtime preference and then the client program tries to complete tasks in that timeframe. Having said that the highest preference allowed at present is 24hrs. So, something is still off.

The new 6.6 BOINC versions do not show CPU time on the task summary page. See my post. You have to select the specific task and look at the properties.

If Rosetta is only getting 10% of CPU, then the figures you have there would only be about 5 hours of actual CPU time. So what is limiting the CPU time available to BOINC? Could be other tasks running at higher priority then BOINC's low priority. Could be BOINC preferences to limit number of CPUs or % of CPU time.

I have all my projects running with no restrictions, all set to the same priority, and set to use 100% of the cpu. Is there something I'm missing?

---

Apparently you are missing that there is a Rosetta specific preference for work unit runtime. You view and set this for each venue on the project website. The BOINC Manager does not show project specific values.

So... are you using a 6.6.x version of BOINC? If so, what is shown in the properties for the Rosetta task for CPU time used and how does that compare to the elapsed time?

---

Rosetta Moderator: Mod.Sense

Apparently you are missing that there is a Rosetta specific preference for work unit runtime. You view and set this for each venue on the project website. The BOINC Manager does not show project specific values.

So... are you using a 6.6.x version of BOINC? If so, what is shown in the properties for the Rosetta task for CPU time used and how does that compare to the elapsed time?

I set the preferences for each process to run the same. I am using Boinc 6.6.20. Since I aborted the Rosetta work, it hasn't downloaded any new work...

---

Mini 1.71 is doing it again. CPU usage is down to 50% with Rosetta running on one and Poem running on the other. Performance Manager shows Poem using 50% and Rosetta using 0%. Is it time to Suspend Rosetta again, or is this normal?

---

BTW - Rosetta has been running for 12 hours and with only 28% completed, and 17 hours to go. Should I abort and wait for Rosetta to solve the issue (if there is an issue)?

I also noticed that Rosetta has one unit waiting to run that is 80% complete in 2.5 hours with .5 hours remaining. Why does it run fine and another unit gets stuck?

BTW - Rosetta has been running for 12 hours and with only 28% completed, and 17 hours to go. Should I abort and wait for Rosetta to solve the issue (if there is an issue)?

I have had a number of these where three work units are working fine and the fourth is just marking time with no cpu usage. I have found the only remedy is to reboot the machine. This seems to kick start the errant unit and it completes satisfactorily.

I have tried just closing Boinc (v.6.6.20) but the work units remain running leaving a reboot my only option.

---

I have tried just closing Boinc (v.6.6.20) but the work units remain running leaving a reboot my only option.

Sometimes the simplest explanation is the best...

I had another unit showing 22% complete after almost 4 hours. I restarted and it now shows 22% complete, but now shows that it has run for 1.5 hours, not 4.

Thank you!

---

It's doing it again. Rosetta showed a work unit having 6% completed after 12 hours with 32 hours remaining. Suspending work accomplishes nothing, so I restarted. Same work unit shows 6% complete after 19 minutes, with 3 hours remaining. My question is this: did that work unit struggle for 12 hours to complete 6% or is that a misrepresentation of actual time?

Happy Father's day to all.

It's doing it again. Rosetta showed a work unit having 6% completed after 12 hours with 32 hours remaining. Suspending work accomplishes nothing, so I restarted. Same work unit shows 6% complete after 19 minutes, with 3 hours remaining. My question is this: did that work unit struggle for 12 hours to complete 6% or is that a misrepresentation of actual time?

Happy Father's day to all.

For some reason, probably known to the Boinc Developers but not to us users, this happens and the only thing to do is what you did. It has happened before, probably will happen again, and happens across many projects. This brings it down to a Boinc thing, not a project or user thing. Somehow, for some reason, Boinc forgets what it is doing and just kinds cruises thru not doing any crunching but accumulating clock time. As you said though, usually only on one unit of a multi-core machine. Not every unit, just some and not often enough to debug the problem by the ordinary user!

---

For some reason, probably known to the Boinc Developers but not to us users, this happens and the only thing to do is what you did. It has happened before, probably will happen again, and happens across many projects. This brings it down to a Boinc thing, not a project or user thing. Somehow, for some reason, Boinc forgets what it is doing and just kinds cruises thru not doing any crunching but accumulating clock time. As you said though, usually only on one unit of a multi-core machine. Not every unit, just some and not often enough to debug the problem by the ordinary user!

...except that it only happens with Rosetta.

---