Have enough RAM on the slave that you can run your jobs plus Jenkins + some for
overhead.
(e.g. 1GB of Jenkins slave, + #executors * ( 2GB for Maven +2GB for unit tests
in forked VM) + OS overhead)
Although this amount is mostly an overkill setting it too close to the
threshold will slow your
Thanks...I unfortunately can't be in the UK for the event.
So if the amount of RAM is fixed (4GB), what is a good rule of thumb for
determining what to allocate to the slave process, how many executors it
can reasonably support, etc?
I realize there are a lot of other variables but any starting
I would never advise more than one executor per slave :-o
At some point there will be unit test failures in a project as it has
badly written unit tests that blindly assume they can use port 12345 (and
it will be in use for a different job - and then fight each other). And it
will be the