On Monday, October 22, 2012 4:12:15 PM UTC-5, Jakov Sosic wrote: > > On 10/22/2012 09:04 PM, Bostjan Skufca wrote: > > Hi, > > > > I was just wondering what is someone else's number of manager resources > > and catalog run time. > > Mine is 1,700 resources and average catalog run of 70-100 seconds (40 > > seconds for catalog retrieval, 30-60 for catalog run), depending on the > > network distance between puppetmaster and managed node. > > Then there are few more seconds for provider cache stuff, and report > > uploading takes it's tool too, together adding some 20 seconds. > > > > Care to share your puppet agent performance details? > > We're not as near in the number of resources per node yet, so no point > in comparing :) Let's just say my client run is less then 10 seconds on > average :) > > > But as a side note, I'm wondering at what number of nodes one must > replace puppetmaster with Apache+Passanger? Just a rough estimate, let's > say master runs on 2 socket quadcore. > > I replaced it at around 35 nodes I think. I've currently got 42. Before making the change to Apache + Passenger, we were seeing timeouts with webrick.
And in all honestly, I would make that change if you were using puppet in any sort of production environment. The only time I use webrick is for throwaway VMs where I have 1-3 nodes (including the master itself) running off a master so I can test something outside of my main master. > Is it 50 agents? 100 agents? 200 agents? > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/Uwq22fPQi5gJ. 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-users?hl=en.
