I used the <project_max_concurrent> line in the app_config.xml file to only allow the computer to run a single task at a time. And it did actually finally complete two tasks so far (running one at a time) after about 12.5 hours each. So it looks like they can actually finish successfully on CPU, it just takes a LOT longer than the 30 minute target goal in the preferences settings. And probably a huge amount longer if running multiple tasks at the same time.

---

I used the <project_max_concurrent> line in the app_config.xml file to only allow the computer to run a single task at a time. And it did actually finally complete two tasks so far (running one at a time) after about 12.5 hours each. So it looks like they can actually finish successfully on CPU, it just takes a LOT longer than the 30 minute target goal in the preferences settings. And probably a huge amount longer if running multiple tasks at the same time.

Just on it's own, the TTAFold would have used 100% of your CPU, that fact that it was showing as 30-70% indicates there were other things (other BOINC projects?) trying to use the CPU at the same time, hence the extra long processing time. Otherwise your crunching time should have been around the 4 hour mark or there abouts.


With the current application, they have set it so that it reserves 1 CPU thread to support the GPU Task.
Now they need to make it so that people can get CPU work, and they need to limit the CPU processing to one or 2 threads, making BOINC aware of the number required. And ideally then give people the option to increase or decrease that number in the Ralph project configuration in their account.

---

Grant
Darwin NT

New app was released and there are new tasks

0.03 (nvidia_alpha)

---

--
I crunch for Ukraine

I used the <project_max_concurrent> line in the app_config.xml file to only allow the computer to run a single task at a time. And it did actually finally complete two tasks so far (running one at a time) after about 12.5 hours each. So it looks like they can actually finish successfully on CPU, it just takes a LOT longer than the 30 minute target goal in the preferences settings. And probably a huge amount longer if running multiple tasks at the same time.

Just on it's own, the TTAFold would have used 100% of your CPU, that fact that it was showing as 30-70% indicates there were other things (other BOINC projects?) trying to use the CPU at the same time, hence the extra long processing time. Otherwise your crunching time should have been around the 4 hour mark or there abouts.

Nope. Absolutely nothing else was running on that computer. It is a pretty old CPU (i7-4790) so longer run times are expected. But it was definitely a lot longer than the target time.

---

New app was released and there are new tasks

0.03 (nvidia_alpha)

They disappeared quickly, but as far as I can tell there were zero errors on my RTX 3060Ti and on my Quadro P5000 cards.

---

I used the <project_max_concurrent> line in the app_config.xml file to only allow the computer to run a single task at a time. And it did actually finally complete two tasks so far (running one at a time) after about 12.5 hours each. So it looks like they can actually finish successfully on CPU, it just takes a LOT longer than the 30 minute target goal in the preferences settings. And probably a huge amount longer if running multiple tasks at the same time.

Just on it's own, the TTAFold would have used 100% of your CPU, that fact that it was showing as 30-70% indicates there were other things (other BOINC projects?) trying to use the CPU at the same time, hence the extra long processing time. Otherwise your crunching time should have been around the 4 hour mark or there abouts.

Nope. Absolutely nothing else was running on that computer. It is a pretty old CPU (i7-4790) so longer run times are expected. But it was definitely a lot longer than the target time.

If you ever get CPU Taks on it again i'd check Tasks Manager when one is running.
On my 12 thread system, a single CPU Task used 8 threads. So on that 8 thread system, i'd expect CPU usage to be 100% just for the single Task. The fact it was lower (and very variable), and took such a long time indicates something else was there using CPU time as well.

---

Grant
Darwin NT

If you ever get CPU Taks on it again i'd check Tasks Manager when one is running.
On my 12 thread system, a single CPU Task used 8 threads. So on that 8 thread system, i'd expect CPU usage to be 100% just for the single Task. The fact it was lower (and very variable), and took such a long time indicates something else was there using CPU time as well.

That's exactly what I did before, and where I got the numbers that I reported here.

A single Ralph CPU task running on the 4 core/8 thread i7-4790. Absolutely nothing else running on the computer, and therefore nothing else using the CPU. Not in BOINC and not outside of BOINC other than the normal few percent now and then from Windows processes. That one task was varying between about 30% and 70% CPU usage while I was watching it. Of course I didn't watch it the entire 12+ hours so it might have been close to 100% at some point, but it definitely didn't stay anywhere close to 100% over the 30 minutes or so that I was actively watching it.

---

A single Ralph CPU task running on the 4 core/8 thread i7-4790. Absolutely nothing else running on the computer, and therefore nothing else using the CPU. Not in BOINC and not outside of BOINC other than the normal few percent now and then from Windows processes. That one task was varying between about 30% and 70% CPU usage while I was watching it. Of course I didn't watch it the entire 12+ hours so it might have been close to 100% at some point, but it definitely didn't stay anywhere close to 100% over the 30 minutes or so that I was actively watching it.

That is very odd.

On my system, the Single Task used it's 8 threads pretty much all the time. It dropped a bit, every now and then, but never down to 70%, let alone 30%. That would have been over a 10 min period, every now and then for 10-20 seconds when checking on things.

---

Grant
Darwin NT