Thanks a lot.
It's an important piece of news.
Now balancing between sub-projects will be easier because all the sub-projects have the same level.
I hope it will avoid if a sub-project fails to stay stuck with it and server will provide other sub-project jobs, without micro-managing inside our web preferences.
It would be a good thing to adapt the flow in such circumstances (failure , overload ,lack of wus).
So we have to modify our web preferences to enable a maximum of sub-projects, (if our hardware configuration has the requirement expected...).

I can't answer you.
But i find intersting what you are doing.
Can you give us the maximum of the memory used parameter in the top console (alt+F3) inside the Vm for 2-core ? (Theory , CMS , LHCb)
It may be interesting for small hosts which would want to test if 2-cores are possible or not with their ram.They would have to add 50 MB to your numbers and place them in their app_config.
Normaly the maximum of the parameter is reached after the vm is filled with the end of the net - initialisation (not necessary to wait and see all the time).
Curiously ,you use a higher amount of ram in your app_config than needed.
The initial purpose of multicore wus was to allow small hosts with less ram to do more work than with single core which requires more ram.
I don't know if giving more ram speed up the job.It seems not.
But i noticed the last job theory done with 2-core i ran used 130 % of a core that is to say the second core help to finish the job.
It seems processes are shared in particular condition between cores...
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Another question :
can someone explain why when we put