I can get max three workunits running simultaneously. One OONI, one PERF and one CNOD. Sometimes there are only two of them. But I have 12 cores available, only three used by Asteroid@home. Since iThena.Measurement tasks aren't cpu intensive (their load is almost zero), and I see that they don't take up my internet bandwith either (however I have a huge bandwith at disposal), why never more than three?
--
Bye, Lem

One per project is a BOINC restriction AFAIK as it is not set up to queue workunits.

---

Paul.

Run multiple clients. Thats how people get a hundred million credit

Run multiple clients. Thats how people get a hundred million credit

Buy more computers, and let them all run BOINC. That's how I do it. Try to get as many different BOINC Platforms as possible (Windows, Linux, Android, FreeBSD combined with preferably both x86 and ARM -whatever your project(s) support).

---

I can get max three workunits running simultaneously. One OONI, one PERF and one CNOD. Sometimes there are only two of them. But I have 12 cores available, only three used by Asteroid@home. Since iThena.Measurement tasks aren't cpu intensive (their load is almost zero), and I see that they don't take up my internet bandwith either (however I have a huge bandwith at disposal), why never more than three?
--
Bye, Lem

The number of cores you have is irrelevant as it a "Non CPU Intensive" work unit, that is it runs in memory, which is why only one per BOINC instance.

Conan

---

Run multiple clients. Thats how people get a hundred million credit

Yeah, mostly wankers. Or it's humorous and I accept it.