ok I see the message is far from ideal. We will change it.
What it actually means is that you should increase the “number of processors” and potentially also reduce the “number of parallel processors” as seen here:
first value defined
The defines in which cloud instance your solution will be computed on, so implicitly also the total amount of RAM available. This is then distributed evenly across all parallel processes, so each process will get 1/n times the total RAM if you use n parallel processes.
Obviously if you use more procs in parallel this will increase the simulation speed, but also reduce the RAM available per parallel proc and as the performance never scales linearly, there is kind of a trade-off to make.
We are currently actually working on an automation of this, so in the future you should not be concerned any more.
For now I would say whenever you see this message, double the “number of procs” and leave the “number of parallel procs” as they were - so from 4 - 2 you switch to 8 - 2.
I hope this helps.
Regarding run 3, I will need to check more in depth, it seems to be a specific issue with the 1-core instance.