'lo, ----- "Markus Roberts" <[email protected]> wrote:
> Aurelien -- > > Thank you! > > > > > I noticed that the time needed by puppetd to write on disk its cached > catalog has increased a lot in Puppet 0.25. > > I'm using 0.25.4 and, with a catalog with around: > ~400 resources: i need 3 sec to write this on disk > ~900 resources: i need 8 sec > ~1900 resources: i need 21 sec. > > > So slow and getting slower (though the r^2 term is ~0.001, so it's not > the dominating factor at this point). Can you describe your test setup > in a bit more detail? > > > > I really have catalogs with 900 resources, in production., 1900 was > only to test the problem. > But I'm sure this value will increase. > > > Yes, that seems reasonable; it would be surprising if it didn't from > that point, since you're past where any economies of scale might > plausibly kick in. > > > > I do not reproduce this issue with Puppet 0.24. > > > Meaning, I assume, that it was not noticeably slow or that you were > unable to measure it? > > And, again, thank you for taking the time to do these measurements; > it's quite helpful as we prepare to roll out 2.6 to get feedback on > where we are going in the right or wrong direction historically. I might be wrong, but at the moment we take a PSON encoded catelog from the master, decode it, then recode it into YAML and save it to disk? I think I recall a ticket going past recently to get rid of that second recode to YAML and just save the original PSON catelog to disk as a cache, or am I remembering wrong? -- 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.
