+1 - that'd be fantastic. I'd love to help with that. A.
On Thu, Oct 1, 2015 at 4:50 AM, Michael Neale <michael.ne...@gmail.com> 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 jenkinsci-dev+unsubscr...@googlegroups.com. > 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPbPdOaLf62SY2gR7c-fzudi6yT44wvtnj2rhFCGJ1UEtGng3Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
