First, Émile, your performance plots are awesome! Thank you so much for taking the time to put these together. They will help us tremendously as we investigate and kill off these issues.
Second, we recognized the performance drop prior to this thread and Max and Carl had already been doing outstanding work to isolate, categorize, and prioritize the various problems. Third, we take these performance problems seriously and are committed to fixing them. Significant internal discussions have been taking place, though outside this public forum. We are neither ignoring this problem nor giving up. If we have appeared unresponsive, it's not because we don't think it's important, but rather because we failed at communicating how important it truly is. Bottom line: Performance is critical. We will fix the problems. Fourth, Peter, Émile, and Trevor (or anyone else experiencing the problem), would you be willing to be pre-release testers of improvements? Our ops team is seeing the problem too, but that's only a single real-world data point. We need to make sure we don't self-optimize. We need your help to make sure the performance fixes address *your* problems not just ours. Fifth, thank you for keeping this issue in the spotlight. If something seems "off," please don't just assume that's how it's supposed to be. A delightful user experience is a core Puppet Labs value. If something doesn't work the way you think it should then we need to make our user experience better, not beat you into submission. We will undoubtedly make decisions that adversely affect a small number of individuals in, hopefully, only a minor way, but performance is not, and will not be, one of those tradeoffs. Sixth, if you are not getting the timely response you think you should, please feel free to publicly shame me (or anyone else at Puppet Labs) for not engaging you. Something like this would be awesome: "Dammit, Jeff! I thought you guys were working on this, but I haven't seen anything in a while. Give us a build to test already!" -Jeff ---- Jeff Weiss Software Developer Puppet Labs, Inc. jeff.we...@puppetlabs.com On May 9, 2012, at 2:15 AM, Peter Meier wrote: >> Otherwise i work on Puppet optimizations and i have seen some strange things >> too. I work on big catalog (more than 1000 resources) and i want to reduce >> the application time (around 20 sec). >> I have seen two kind of things: >> - First, recent Puppet versions are slowest (see PuppetVersions.png in >> attachment), mainly the last one: 2.7.12. > > I can confirm that. > > It's one of the reasons I'm still on 2.6 at a lot of places, as I have a > 10-20% catalog compilation time increase with 2.7. Even with a master > pre-2.7.12 (might have been 2.7.1 or so), which is what I tested and I never > read it got better, hence I never retested it. > >> - Second, ruby 1.9.3 is very slow compare to ruby EE (see PuppetRuby.png in >> attachment). I think the problem come from the yaml library: caching catalog >> is very slow. > > It is interesting that 1.9 is slower. > > But anyway I remember that caching the catalog (read serializing it as yaml > to disk) has been very slow for years and also known. It usually makes the > agent look like it's hanging. This especially happens on huge catalogs - I > have catalogs with up to 10k resources. > > Having a puppet release focused on stability and performance would really be > appreciated. I think there could some room for improvements at various places. > > ~pete > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" group. > To post to this group, send email to puppet-dev@googlegroups.com. > To unsubscribe from this group, send email to > puppet-dev+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-dev?hl=en. > -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to puppet-dev@googlegroups.com. To unsubscribe from this group, send email to puppet-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
