This is the crux of the situation for me too - Puppetlabs blame it on a Ruby bug that hasn't been resolved with RHEL6 (in my situation) but this wasn't an issue until .3 for me too. I feel that fact that many of us have this problem since upgrading means it can be fixed within Puppet, rather than Ruby, because it was fine before.
On Tue, Feb 1, 2011 at 5:31 AM, Waechter Udo <udo.waech...@uni-osnabrueck.de > wrote: > Hi, > > On 31.01.2011, at 22:50, John Warburton wrote: > > > On 1 February 2011 08:43, Brice Figureau <brice-pup...@daysofwonder.com> > wrote: > > On 31/01/11 19:11, Udo Waechter wrote: > > > > Do you use storeconfigs? > > > > Speaking of resource hogs, do you run the puppet labs dashboard on the > same host? I had a similar setup (on crusty old Sun kit mind), and found a > big performance hit in writing the reports by the client to the puppet > master and then those reports to the dashboard. Everything calmed down once > I moved the dashboard to another host > > Yes I do, but I always did.... Even if this is not a good idea, performance > was acceptable until 2.6.3 Something must have changed there. > --udo. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
