Set the run time to 24 hours in an attempt to prevent any Rosetta-mini d/ls but yet 8 more showed up on various machines.

Any server side setting that can accomplish this?

Local app_config.xml can only limit to minimum 1 WU with <max_concurrent>; 0 is not parsed and used. Sometimes a trick to set max_mem intolerably low can cause unwanted WU to die in seconds and get a backoff from the server; but I want the large WU so my bag of tricks is empty... or is it... hmmm.

Maybe I could set the core count for mini's to greater than the client's core count so they never run although they will clog up the work cache.

Something like this for an 8 core client:

<app>
<name>minirosetta</name>
<max_concurrent>1</max_concurrent>
<fraction_done_exact/>
</app>
<app_version>
<app_name>minirosetta</app_name>
<avg_ncpus>9</avg_ncpus>
<cmdline>-t9</cmdline>
</app_version>

Is -t command switch implemented for Rosetta WU's?

Maybe I could set the core count for mini's to greater than the client's core count so they never run although they will clog up the work cache.

No, this won't work. I tried that on Milkyway to avoid single core n-Body WUs. BOINC will still run them, but just one at a time.

Set the run time to 24 hours in an attempt to prevent any Rosetta-mini d/ls but yet 8 more showed up on various machines.

The "mini" WUs will also run 24 hours. It's just a name, there's nothing mini about them, actually they are even a bit larger than the "normal" Rosetta WUs, when it comes to memory use. Or is there any other reason, why zou don't want them?

---

.

there's nothing mini about them, actually they are even a bit larger than the "normal" Rosetta WUs, when it comes to memory use

Then why are they referred to as 'mini'?

Or is there any other reason, why zou don't want them?

Only real reason is WUProp, mini's are currently well over 10,000 hours but regular just broke 1000.

I want 100,000 hours on all WU's my machines take on for my epic purple badge.

I noticed these WU's do love to eat RAM and had to limit them to <max_concurrent>1</> so that makes breaking 100,000 hours some 3 to 5 years off for Rosetta unless I find money for more cores and not being able to control the mini vs regular means wasted hours on one.

I noticed these WU's do love to eat RAM and had to limit them to <max_concurrent>1</> so that makes breaking 100,000 hours some 3 to 5 years off for Rosetta unless I find money for more cores and not being able to control the mini vs regular means wasted hours on one.

Have you tried <max_concurrent>0</max_concurrent> for the mini application?

Or app_info.xml (anonymous platform) with only the "big" rosetta application?

BTW, you need more RAM and not more cores.

---

.

Have you tried <max_concurrent>0</max_concurrent> for the mini application?

On LHC@home in 2016. BOINC main forums help desk said that the client ignores a 0 setting.

Or app_info.xml (anonymous platform) with only the "big" rosetta application?

I'll look into this.

BTW, you need more RAM and not more cores.

Well normally, but I can't compete for mag as well on Rosetta as I can on other projects so Rosetta is a backup project which will never get all my cores.

I wanted to dedicate my Android tablet's core to the 100k hour goal but it's never gotten a single WU.
Need to look into why.

I wanted to dedicate my Android tablet's core to the 100k hour goal but it's never gotten a single WU.
Need to look into why.

This will not add hours to the "Rosetta" application, "Rosetta for Android" is a separate application as you can see on the applications page. But most of the time there are no WUs available.

---

.