This is all so very confusing. Usually people are doing their best to make sure their build server is running as FAST as possible, giving it a dedicated server, fast SSD disk and plenty of RAM. You're asking how to make it run as slow as possible so it won't disturb other applications on the same server. Wow!
Depending on the operating system and the way you have installed Jenkins, you may be able to tune the Jenkins startup. If you are using some Unix variant, you could e.g. add "nice +19" at the beginning of the java command in the jenkins init script. You will also want to tune the java memory parameters. By default java can grab a lot of memory, causing the server to start swapping. Again, how exactly you do that depends on how you installed Jenkins and on what operating system. -- Sami 2012/6/13 Roberto Nunnari <nunni...@gmail.com>: > Hi everybody. > > I wonder how heavy the build processes are on the cpu.. > > I set up a single machine offering many different services (also including > jenkins webapp) and I'm worrying a bit about overall performance when > jenkins will enter production stage. > > Being a virtual machine, I will be able to add one virtual cpu if the load > will be too much.. but I wonder if it also possible to set some > configuration option so that the build processes are started with a high > nice value. Another option I can think of would be to start jenkins main > process with a nice value, but I don't know if that will be considered when > jenkins will span the build processes. > > So.. > 1) build processes can be run at a lower priority? > 2) If yes, how? > 3) build processes will be run one at a time or more than one in parallel? > > Could anybody please cast some light on this? > > Thank you and best regards.
