There are some hairy reasons for running a job on the master, specifically if you need to mess with Jenkins internals. If you don't need to do that (and if you have to ask, you don't), just reduce the number of executors on the master node to zero and see what breaks ;^>.
Also (and you probably know this) you may have to explicitly set the memory settings on the JVM as well as the VM; Java won't take all your memory by default, and you might want to leave a GB or so free so that the OS can do its OS-y things. Basically, if the JVM gives an out of memory complaint, think about the JVM settings first--adding 64GB to your host won't help if Java is only taking 4GB of it. --Rob -----Original Message----- From: Les Mikesell [mailto:lesmikes...@gmail.com] Sent: Wednesday, November 12, 2014 12:12 PM To: jenkinsci-users Cc: Rob Mandeville Subject: Re: Specs for new Master server On Wed, Nov 12, 2014 at 8:21 AM, David Brooks <dkbro...@gmail.com> wrote: > Hi Rob, rginga - > > Excellent information, exactly what I was hoping to see. > > For the RAM requirements, would it be safe to estimate the required > RAM on the master by looking at the combined utilization of the build > servers? For instance, I see that the Jenkins and Java processes > combined are using about 8GB of ram on one of our build servers. > Would this this translate directly to the master utilization? So just > add up the utilization for the build servers and that is the baseline for the > master? > > If so then this machine is going to need TONS of ram. Or I am going > to have to start pruning how much Jenkins 'remembers' about builds. > That may not go over very well with the teams. RAM use will have 'something' to do with the total number of jobs and the number of builds retained for each, but won't be equivalent to adding the whole JVM usage across multiple machines. But if you are using VMs you shouldn't have to be that precise in your initial setup as long as you don't overcommit the physical host. I'd just pick one of the existing servers as the master, move the jobs there and connect the others as slaves. You can do that piecemeal and adjust resources if you see a problem. And I'd recommend not running any jobs on the master itself, just on general principles. -- Les Mikesell lesmikes...@gmail.com Click https://www.mailcontrol.com/sr/o!P5to5kZQnGX2PQPOmvUjg7ce8j6mWJPVy6vlyKvt9qEDX2TVKozQAM3OsLei9cDZBLv8O0BTTBcfXS4znW5Q== to report this email as spam. -----Original Message----- From: Les Mikesell [mailto:lesmikes...@gmail.com] Sent: Wednesday, November 12, 2014 12:12 PM To: jenkinsci-users Cc: Rob Mandeville Subject: Re: Specs for new Master server On Wed, Nov 12, 2014 at 8:21 AM, David Brooks <dkbro...@gmail.com> wrote: > Hi Rob, rginga - > > Excellent information, exactly what I was hoping to see. > > For the RAM requirements, would it be safe to estimate the required > RAM on the master by looking at the combined utilization of the build > servers? For instance, I see that the Jenkins and Java processes > combined are using about 8GB of ram on one of our build servers. > Would this this translate directly to the master utilization? So just > add up the utilization for the build servers and that is the baseline for the > master? > > If so then this machine is going to need TONS of ram. Or I am going > to have to start pruning how much Jenkins 'remembers' about builds. > That may not go over very well with the teams. RAM use will have 'something' to do with the total number of jobs and the number of builds retained for each, but won't be equivalent to adding the whole JVM usage across multiple machines. But if you are using VMs you shouldn't have to be that precise in your initial setup as long as you don't overcommit the physical host. I'd just pick one of the existing servers as the master, move the jobs there and connect the others as slaves. You can do that piecemeal and adjust resources if you see a problem. And I'd recommend not running any jobs on the master itself, just on general principles. -- Les Mikesell lesmikes...@gmail.com Click https://www.mailcontrol.com/sr/o!P5to5kZQnGX2PQPOmvUjg7ce8j6mWJPVy6vlyKvt9qEDX2TVKozQAM3OsLei9cDZBLv8O0BTTBcfXS4znW5Q== to report this email as spam. This e-mail and the information, including any attachments it contains, are intended to be a confidential communication only to the person or entity to whom it is addressed and may contain information that is privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender and destroy the original message. Thank you. Please consider the environment before printing this email. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
