Dave, I am not as informed as others in this group, but my experience has been that the master does very little work as compared to the slaves. Yes, build logs and archived files are uploaded from a slave to the master, but I have not run into any issues with IO performance.
I run a Windows master as a VM running Server 2008 R2 Enterprise, 16 Gb RAM, 4 CPUs, and a 250G disk. I do have to monitor the disk usage by setting build retention values and sizes of artifacts archived. We run 22 slaves (Mac and Windows) and perhaps another 20 on again, off again slaves and, I don’t know, 100’s of jobs. You will need to set executors numbers on your new slave build machines to match their capacity. From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of David Brooks Sent: Wednesday, November 12, 2014 8:44 AM To: jenkinsci-users@googlegroups.com Subject: Specs for new Master server I have searched the archives and don't see a direct answer to this question. I apologize if this has already been asked and answered. My team currently runs a few Jenkins stand-alone build servers, lots of jobs each, some CI jobs, not a lot of concurrency in builds, but some. I have been asked to migrate our environment to a master/slave setup so the job management can be run from one server. My questions is this: what kind of hardware would a master-only machine need to be successful? The current stand-alone servers will become the slaves. So here are the questions I am starting with: * It seems from what I have read in this and other forums that it is a good idea to have one CPU core per executor. Is this true for the master as well as the server doing the builds? Or can we scale back? * I have also read that the master can become I/O bound while moving the logs and build results around. (I think I have that right but some threads suggest that Jenkins can become CPU bound as a result of being I/O bound, an interaction that I don't fully understand.) The network backbone isn't an issue but I can spec out a variety of different storage solutions. I would obviously like to avoid spending money on storage we don't need but I need to build something that will function. * How much RAM should this master-only machine have? * All of our servers are virtual. That helps in that they can be rescaled if needed, but are there any special considerations that a virtual master introduces that I should know about? * Is there anything that I should be thinking about when converting the stand-alone servers to slaves? I have already modeled the process of getting a Jenkins server to be both a stand-alone server and a slave so that I can do the migration without bringing the servers down. That works fine. But is there anything about being a slave server that would change the system requirements? I know I haven't provided enough details to come up with a spec, and that is sort of intentional. I hope to learn instead how to do the analysis, what the tradeoffs are, what the design considerations are, etc. so I can build the spec. This won't be the last time I have to visit this environment and I would like to build the knowledge and skills necessary to be able to manage it. Thanks for any suggestions! ~ Dave -- 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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>. For more options, visit https://groups.google.com/d/optout. -- 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.
