I noticed that Rosetta often is switched to high priority at the beginning of the processing of any workunit.



But as you can see 18% of that unit only tool 4,5h. So all in all it should roughly need another 20h of work. With the deadline being 9 days ahead that would only be 2h a day and BOINC is run much longer.

After a day or so things get back to normal and the high priority is disabled.

I'm using Boinc 6.4.5 and the last benchmark turned out about 2500 (Whet) and 4200 (Dhry).

Is that a problem with Rosetta or is it Boinc?

Version 6.4.5's buggy scheduler is likely causing it. Unless you need 6.4.5 to run CUDA apps, consider dropping back to 6.2.19. On the other hand, if your tasks are getting returned on time and there are no other problems then you might consider it going to high priority mode to be just a minor annoyance that doesn't really warrant going back to 6.2.19.

---

BOINC FAQ Service
Official BOINC wiki
Installing BOINC on Linux

buren, for whatever reason, BOINC is estimating that the task will take another 91 hours to complete, and so it thinks it's best to get started soon! As you have seen, it won't actually take 91 hours. The watchdog will help ensure that as well.

Sounds like your DCF for Rosetta has not settled in yet. But it will with time. You should see the estimated time to completion eventually settle in to match your 24hr Rosetta runtime preference.

---

Rosetta Moderator: Mod.Sense

High priority only means that the task will be run ahead of other tasks. It has no other effect on the system. In other words, it does not take more CPU nor run the task at a higher OS priority. It only means that the BOINC scheduler will run this task in preference over other BOINC Tasks ...

I noticed that Rosetta often is switched to high priority at the beginning of the processing of any workunit.



But as you can see 18% of that unit only tool 4,5h. So all in all it should roughly need another 20h of work. With the deadline being 9 days ahead that would only be 2h a day and BOINC is run much longer.

After a day or so things get back to normal and the high priority is disabled.

I'm using Boinc 6.4.5 and the last benchmark turned out about 2500 (Whet) and 4200 (Dhry).

Is that a problem with Rosetta or is it Boinc?

It is a Boinc thing and as Mod Sense wrote it is a DCF or Duration Correction Factor thing. This can be found in your client_state.xml file. The line looks like this <duration_correction_factor>0.813083</duration_correction_factor>. However yours will have a 90.??????? or something like that. If you wish to see better numbers you can exit Boinc, and manually edit the file and change the number to say 1.000000 for example. This will only change the time Bonc thinks it will take to complete the tasks. If you have multiple projects, then it will be in each of them and each will have a different number, BE CAREFUL to only edit the right one, if you hose to do that. As Paul D. Buck stated though, if you just leave it alone it will eventually fix itself. Although it may take a while. I had a quad core do this and got to the point only one core was running, I manually edited mine and all is good again.

---