I have an E5-2620 server with one 12 core CPU and 32GB memory. The OS is windows 2012 server. The minirosetta version is 3.7.3

I found that some minirosetta process will auto pause after a few hours.These process are show in windows task manager with 0% CPU occupy. These task's status are runnining in boinc manager. Some of these pause task have "--" as estimate end time and some have normal estimate time.After I close boinc client these paused process are stay in process. So I kill them and restart boinc then all minirosetta will run normally.
I have set 16gb memory for minirosetta and I think it is not cause by lack of memory.
Anyone help me so that my I can use all CPU of my server to calculate for rosseta unattend?

The BOINC Manager has a quirk where if your preferences state a maximum CPU % that is not 100%, some tasks get stuck like you described. Note that I am not talking about the % of processors entry.

If you are trying to keep a reserve of CPU available on the machine, I'd suggest doing so by using the % of processors entry. 91% of processors should be 11 of the 12 cores. Leaving one available at all times for other work requests, in addition to the other 11 all running at low priority.

---

Rosetta Moderator: Mod.Sense

The BOINC Manager has a quirk where if your preferences state a maximum CPU % that is not 100%, some tasks get stuck like you described. Note that I am not talking about the % of processors entry.

If you are trying to keep a reserve of CPU available on the machine, I'd suggest doing so by using the % of processors entry. 91% of processors should be 11 of the 12 cores. Leaving one available at all times for other work requests, in addition to the other 11 all running at low priority.

It seams that it occur on windows 2012 server, I have install a virtual machine to run boinc.
Thank you very much.

Oh! Now THAT's an idea. Just to clarify for future readers...

I believe you are saying that you created a virtual machine, allocated the desired amount of CPU to it, and then installed BOINC Manager within the VM, and told it to use "100%" of CPU.

Please make an update after a few days and confirm this circumvents the BOINC Manager problem with "running" tasks getting no CPU.

---

Rosetta Moderator: Mod.Sense

Oh! Now THAT's an idea. Just to clarify for future readers...

I believe you are saying that you created a virtual machine, allocated the desired amount of CPU to it, and then installed BOINC Manager within the VM, and told it to use "100%" of CPU.

Please make an update after a few days and confirm this circumvents the BOINC Manager problem with "running" tasks getting no CPU.

OK, I have created a CentOS virtual machine under Windows 2012, then I install the BOINC in CentOS and run minirosseta, now everything is fine.

Oh! Now THAT's an idea. Just to clarify for future readers...

I believe you are saying that you created a virtual machine, allocated the desired amount of CPU to it, and then installed BOINC Manager within the VM, and told it to use "100%" of CPU.

Please make an update after a few days and confirm this circumvents the BOINC Manager problem with "running" tasks getting no CPU.

Also I noticed that the minirosetta process will not exit event if I stop boinc client under Windows 2012.I have to kill then with task manager.And the dead task will continue to finish after I restart the boinc client.

I have to resolved it with virtual machine after some days for I need it to be unattendently.
The only problem is that the virtual machine can not detect the CPU usage of host machine and pause the task when the server is busy.So I let only 11 thread of 12 of the CPU work for rosseta.

So how is having the VM improving your outcome? Assuming you had the % of CPU preference set previously and this was taunting the BOINC issue where it seems to lose control of properly allocating CPU time to tasks... Now that you have changed that to 100% of CPU. It would seem that just running BOINC under the normal OS, with at max 11 CPUs and up to 100% of each of those CPUs would still give you the ability to use the setting for BOINC to suspend if other CPU activity crosses a given threshold.

---

Rosetta Moderator: Mod.Sense