I know that max number of concurrent jobs can be set also via an app_ config.xml setting but it would be more convenient to have that setting implemented under the projects preferences like at the project LHC. Since a single wu seems to occupy 830 MB of RAM one of my PCs runs out of memory when allowed to run a full set on all threads.

---

I know that max number of concurrent jobs can be set also via an app_ config.xml setting but it would be more convenient to have that setting implemented under the projects preferences like at the project LHC. Since a single wu seems to occupy 830 MB of RAM one of my PCs runs out of memory when allowed to run a full set on all threads.

I second that.

I hadn't expected that amount of RAM to be required by the project. My machines are equipped with enough RAM but the average computer could reach it's maximum quite soon when crunching these workunits, so having the possibility to set <max_concurrent> or <project_max_concurrent> via the Website would really be neat and possibly help the not so experienced Users.

Yes.

Our calculation requires the creation of a very large matrix of values ​​on the Primesieve library.
95% of the memory goes under the matrix.

Otherwise, we will not be able to calculate what we are looking for.
On my home computer I set use no more 50% RAM and no more 60% CPU and time cpu.

Ok, for everyone who also has a host with limited RAM, you can create an app_config.xml file using an Editor program with the following content:

<app_config>
<project_max_concurrent>6</project_max_concurrent>
<report_results_immediately>0</report_results_immediately>
</app_config>

This example will allow your computer to run 6 work units at once. You can change the "6" for any other number which your machine is cable of handling.
Save the file in pure text format, select "ANSI" coding if possible. It needs to be in the ADSL project folder.
Than go to BOINC manager and select OPTIONS, READ CONFIG FILES

This way you can use the remaining cpu threads for a different project with less memory requiremnts.

I would hold off on doing anything until after the name change or you will probably have to recreate it. After the name change the project directory (which is where the app_config.xml file resides) might change. Alternatively, save a copy in another directory and copy it over after the name change

Yeah, that should be no biggy. Just copy that file into the new directory.