Jeff Weiss a écrit :
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.
You're welcome, share my results with the community is quite natural ;)
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.
Of course, we will test all proposals that improve performances. Émile -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
