I just noticed that the ability to select project has been removed from the account MilkyWay preferences. So no ability to select/unselect N-body or Separation runs independently.

Could we get that choice back again, please.

---

They are working on that.

---

Well I was just about to ask about multithreaded CPU applications. Looks like I no longer have to since they've apparently been phased out.

Well I was just about to ask about multithreaded CPU applications. Looks like I no longer have to since they've apparently been phased out.

An app_config.xml file will let you do it manually if you want too, most cpu apps can be done that way but not all.

Well I was just about to ask about multithreaded CPU applications. Looks like I no longer have to since they've apparently been phased out.

An app_config.xml file will let you do it manually if you want too, most cpu apps can be done that way but not all.

This should work in your app_config.xml for 4 threads (check the client_state.xml for this information).

<app_version>
<app_name>milkyway_nbody</app_name>
<plan_class>mt</plan_class>
<avg_ncpus>4.0</avg_ncpus>
<cmdline>--nthreads 4</cmdline>
</app_version>

Well I was just about to ask about multithreaded CPU applications. Looks like I no longer have to since they've apparently been phased out.

An app_config.xml file will let you do it manually if you want too, most cpu apps can be done that way but not all.

This should work in your app_config.xml for 4 threads (check the client_state.xml for this information).

<app_version>
<app_name>milkyway_nbody</app_name>
<plan_class>mt</plan_class>
<avg_ncpus>4.0</avg_ncpus>
<cmdline>--nthreads 4</cmdline>
</app_version>

Thank you.
Does this work on all CPU projects or only on a few?
I'm curious what the difference between the following is, though.
<avg_ncpus>4.0</avg_ncpus>
<cmdline>--nthreads 4</cmdline>
Aren't these essentially saying the same thing?

thanks!

For understanding what the descriptors do, it is best to refer to the BOINC documentation. https://boinc.berkeley.edu/wiki/Client_configuration#Application_configuration
The part you are interested in the document is listed under the Project-level configuration section.

---

Does this work on all CPU projects or only on a few?

<cmdline>--nthreads 4</cmdline>

<cmdline>--nthreads 4</cmdline> is an actual command line option (could be for numerous other options besides multithreading) passed onto the WU application at startup and syntax depends on the coding culture of the author.
LLR.exe accepts "-t4", not sure it accepts "--nthreads 4"

If you don't pass on the option exactly the way the application expects it, then no multithreading.
If a project's WU doesn't actually have code to multi-thread, then the command line option is meaningless, so it will only work on CPU work units that are ready for multithreading.

(Sorry Keith, that was off topic, but interesting question to be answered)

Does this work on all CPU projects or only on a few?

<cmdline>--nthreads 4</cmdline>

<cmdline>--nthreads 4</cmdline> is an actual command line option (could be for numerous other options besides multithreading) passed onto the WU application at startup and syntax depends on the coding culture of the author.
LLR.exe accepts "-t4", not sure it accepts "--nthreads 4"

If you don't pass on the option exactly the way the application expects it, then no multithreading.
If a project's WU doesn't actually have code to multi-thread, then the command line option is meaningless, so it will only work on CPU work units that are ready for multithreading.

(Sorry Keith, that was off topic, but interesting question to be answered)

That's exactly what I was looking for. The documentation simply provides various config examples without going into too much detail about that option in particular. Thank you for the explanation.

I don't think there are many multithreaded applications around. I haven't gotten one from MWH since I started crunching here again but it's good to know I can invoke it if I so choose (I'm assuming the reference to LLR.exe was what this meant)?

MW used to have a mt N-body application in earlier times. GPUGrid.net currently uses an mt application called QC Chemistry that heavily uses multiple cores with default of <cmdline>--nthreads 4</cmdline>. When the application first was developed it defaulted to using all cpu cores until users complained and it was knocked down to something more sensible.

---

MW used to have a mt N-body application in earlier times. GPUGrid.net currently uses an mt application called QC Chemistry that heavily uses multiple cores with default of <cmdline>--nthreads 4</cmdline>. When the application first was developed it defaulted to using all cpu cores until users complained and it was knocked down to something more sensible.

Well that's interesting. I didn't think gpugrid had any CPU work at all for some reason. Neat.

I remember having MW use all the cores on my fx8350 back in the day.

The QC Chemistry app is only working well for Linux hosts. They are still debugging a QC Chemistry app for Windows hosts.

---

They are still debugging a QC Chemistry app for Windows hosts.

Got 30 machines trying to get a hold of some of those.
Deleted 3 on a machine that got some because I was doing maintenance/rebuild and it would be down for 2 days. I didn't know the rarity.
Another WUProps WU with less than an hour runtime probably stuck on my record....


BTW, the most common WU's with plentiful work are:
SRBase and Primegrid (where ever the LLR.exe app is used) can run multi-threaded but you'll need to setup the app_config.xml
All the LHC@home WU's can multithread, Theory has to be setup for MT and has too much single thread time, but CMS and ATLAS thrive on MT.
YAFU is all multithreaded work (handled by the wrapper), up to 64 cores (maybe more).
Cosmology is VM (boinc2docker) multithreaded as well as any other project using the boinc2docker VM for work, so BOINC TACC (Texas), nanoHUB (both low work).
Amicable Numbers CPU work is minimum 2 cores.
I think CAS@home and BURP are MT, but can't get any work from them to find out. BURP's mission was way more important 10 years ago.

MW used to have a mt N-body application in earlier times. GPUGrid.net currently uses an mt application called QC Chemistry that heavily uses multiple cores with default of <cmdline>--nthreads 4</cmdline>. When the application first was developed it defaulted to using all cpu cores until users complained and it was knocked down to something more sensible.

Primegrid has a ton of cpu apps and MOST can be multi-threaded like that, so can the ones at RakeSearch, SRBase, I think Universe and others I don't remember right now. The easiest thing is to try it and see if it works, you have the basics now just change the app name which is listed under apps on most projects and put the app_config.xml file it in that projects folder.

MW used to have a mt N-body application in earlier times. GPUGrid.net currently uses an mt application called QC Chemistry that heavily uses multiple cores with default of <cmdline>--nthreads 4</cmdline>. When the application first was developed it defaulted to using all cpu cores until users complained and it was knocked down to something more sensible.

Primegrid has a ton of cpu apps and MOST can be multi-threaded like that, so can the ones at RakeSearch, SRBase, I think Universe and others I don't remember right now. The easiest thing is to try it and see if it works, you have the basics now just change the app name which is listed under apps on most projects and put the app_config.xml file it in that projects folder.

Thanks!
I'm assuming if it doesn't support it it simply won't work and will resort to a single thread per WU?

MW used to have a mt N-body application in earlier times. GPUGrid.net currently uses an mt application called QC Chemistry that heavily uses multiple cores with default of <cmdline>--nthreads 4</cmdline>. When the application first was developed it defaulted to using all cpu cores until users complained and it was knocked down to something more sensible.

Primegrid has a ton of cpu apps and MOST can be multi-threaded like that, so can the ones at RakeSearch, SRBase, I think Universe and others I don't remember right now. The easiest thing is to try it and see if it works, you have the basics now just change the app name which is listed under apps on most projects and put the app_config.xml file it in that projects folder.

Thanks!
I'm assuming if it doesn't support it it simply won't work and will resort to a single thread per WU?

It may error some units out, I really don't remember.

I think Universe and others I don't remember right now.

All the LHC@home WU's can multithread,
YAFU is all multithreaded work.
Cosmology is VM (boinc2docker) multithreaded
Amicable Numbers CPU work is minimum 2 cores.

RakeSearch has a user created optimized app that's supposedly faster than mt.

System administrator Eric has fixed the project preferences to restore the ability to select campaigns again. Kudos.

---