Hi Artur, 100MB/s sustained transfers means very little in the context of Jenkins startup (and depending on your workload on running performance).
You need to look at random read io performance (aka read IOPs). I went from 3 hours for a cold startup with 16 * 300GB 10k SAS drives on an internal RAID with 1GB flash cache memory to 3 minutes with a single Samsung 840 SSDs (which is now a RAID 1 pair of these drives) . (Warm startup - service jenkins restart - went from 2 hours to 2 minutes...) The sustained transfer of both setups is in a similar ballpark- the random IO reads puts the SSDs in a different league. There's still however an issue in that Jenkins may be loading too much data for these job types and plugins. I would suggest a quick benchmark when jenkins is shutdown of finding all config.xml files under job directories in jenkins_inst_dir/data and then loading them into memory (cat filename > null) and timing that to see how long it takes (jenkins may well load some more depending on what plugins you have installed). /James From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Artur Szostak Sent: 25 March 2014 14:34 To: jenkinsci-dev@googlegroups.com Subject: RE: Increase logging level to debug 2 hour startup About 600 matrix jobs and 50 free-style jobs. The matrix jobs typically have about 60 sub jobs. Most jobs are triggered with the "Build after other projects are built" option to form a dependency tree. I keep only the last 50 builds for most jobs and only the last 10 successful artifacts, simply to save disk space. I would imagine all this is a rather straight forward use case. In case this is asked: The machine my instance is running on has 24 cores, 64GB or RAM and 2TB or RAID disk space that can sustain ~100MB/s transfers. So how does your setup compare that you get a 2 minute start time? At some point I thought it might be coming from a plugin so I even tried to wipe all the plugins and just have the core jenkins 1.532.2 start. Still got about 2 hours. Cheers Artur ________________________________ From: jenkinsci-dev@googlegroups.com<mailto:jenkinsci-dev@googlegroups.com> [jenkinsci-dev@googlegroups.com] on behalf of Baptiste Mathus [bmat...@batmat.net] Sent: 25 March 2014 13:45 To: jenkinsci-dev@googlegroups.com<mailto:jenkinsci-dev@googlegroups.com> Subject: RE: Increase logging level to debug 2 hour startup How many jobs do you have? You may have a specific typology which triggers that show startup time. There are many installations out there with many thousands jobs and it doesn't seen this takes that much time,I guess it would have been reported if so. For example, we for one have a 600+ jobs installation, and it takes about 2 minutes to start. Cheers Le 25 mars 2014 13:24, "Artur Szostak" <aszos...@partner.eso.org<mailto:aszos...@partner.eso.org>> a écrit : > > filter project type > > I meant, matrix project type, which apparently allows a custom filter > to be specified. So much for lazy loading then. I guess I have no choice but to suffer my 2 hour start up times. This means Jenkins does not scale properly beyond a few hundred jobs. All quite disappointing :-( -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com<mailto:jenkinsci-dev%2bunsubscr...@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 Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com<mailto:jenkinsci-dev+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 Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com<mailto:jenkinsci-dev+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 Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
