Wow fantastic. Actually 3 minutes means that the changes are pretty successful - I doubt there would be a whole lot to optimise in that case right? or could be even more lazy loaded? Still, probably a great example. Taking that base and then adding more plugins and config changes to the mix would also shed light on when things suddenly go bad.
Is there publicly available tarball backups of that JENKINS_HOME or are there secrets in it? On Wed, Oct 7, 2015 at 11:33 PM Andrew Bayer <[email protected]> wrote: > So builds.apache.org is like 1500 jobs plus another ~30k Maven modules > (stupid Maven project type!), $JENKINS_HOME is somewhere around 1tb. Until > recently, startup time was a good 15 minutes or so, but since going from > 1.565 to 1.609 seems to have made a *massive* difference in startup time - > down to like three minutes. > > A. > > On Fri, Oct 2, 2015 at 2:18 AM, Michael Neale <[email protected]> > wrote: > >> Oh wow - they may be a perfect test workload. Do you know if boot up >> times are in the many many minutes for those instances? Some data on the >> jenkins_home dir sizes? >> It would be ideal to use opensource workloads (even if it is a point in >> time) vs something contrived, or a scrubbed version of a private users data >> that has donated it, however it would want to be pretty hefty (not >> necessarily 2TB jenkins_homes that I have heard of, or 40 minute boot up, >> but something up there would be nice). >> >> I guess the next step is an initial scope of what we want to measure. To >> keep things focussed I am thinking or boot up to job load time, and listing >> a few things. >> >> >> >> >> On Thursday, October 1, 2015 at 5:55:08 PM UTC+10, Andrew Bayer wrote: >>> >>> ...and I can most likely provide builds.apache.org's >>> jobs/builds/load/etc as a use case. >>> >>> A. >>> >>> On Thu, Oct 1, 2015 at 9:54 AM, Andrew Bayer <[email protected]> >>> wrote: >>> >>>> +1 - that'd be fantastic. I'd love to help with that. >>>> >>>> A. >>>> >>>> On Thu, Oct 1, 2015 at 4:50 AM, Michael Neale <[email protected]> >>>> wrote: >>>> >>>>> Hey all - I have thought it would be a great idea to have some quasi >>>>> formal "performance lab" setups for Jenkins. >>>>> >>>>> Recently around Jenkins 2.0 planning threads there have been lots of >>>>> comments around performance challenges. Often things like launch time >>>>> (talking many minutes to an hour for large workspaces - launch times are >>>>> probably a good proxy for a whole lot of issues, but there are other >>>>> issues >>>>> too). >>>>> >>>>> At JUC west there was an excellent talk by Akshay Dayal from Google, >>>>> on scaling jenkins. I highly recommend flicking through the slides >>>>> <https://www.cloudbees.com/jenkins/juc-2015/abstracts/us-west/02-01-1600> >>>>> or watching the talk >>>>> <https://www.youtube.com/watch?v=9-DUVroz7yk&index=16&list=PLvBBnHmZuNQKyjKInevHYsRq8J7Q1I6Fq> >>>>> if you have time. >>>>> >>>>> Basically, they had some performance goals and started by setting up >>>>> measurements and test scenarios to validate their progress - both around >>>>> scalability of slaves (an interesting issue) but also on bootup time (time >>>>> to recovery) which is very interesting. It reminded me that to improve >>>>> something like this you kind of need easily repeatable measurements in >>>>> controlled environments, which currently I don't think the Jenkins project >>>>> has set up? (correct me if wrong). >>>>> >>>>> I know Stephen Connolly did some work a few years back on slave >>>>> scalability which was interesting (building out a test suite >>>>> infrastructure), but I am not aware of subsequent efforts. >>>>> >>>>> Is this something people would be interested in? >>>>> >>>>> Having either large sample JENKINS_HOME specimens or test code that >>>>> can generate pathological data would be required, as well as automation >>>>> around running it on a variety of machines (not necessarily cloud, ideally >>>>> want to be testing code not cloud infrastructure). >>>>> >>>>> >>>>> -- >>>>> 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 [email protected]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/jenkinsci-dev/76a12929-8f10-4b50-bf01-04cc77768149%40googlegroups.com >>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/76a12929-8f10-4b50-bf01-04cc77768149%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> 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 [email protected]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/297b9981-edc5-49e2-b46f-f0b49183f32c%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/297b9981-edc5-49e2-b46f-f0b49183f32c%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/1F9DHyMOutw/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAPbPdOZLUVXneHYHL6B9cg912EDbRL3PePRbjWz%2BEgV0jqpf4g%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAPbPdOZLUVXneHYHL6B9cg912EDbRL3PePRbjWz%2BEgV0jqpf4g%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAKVMTi5xCBNyBnXqmHf2azT_Rvaz86c01%3Dkjx19EgxiF%2BVD%2Bng%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
