On Wed, 2012-05-09 at 11:15 +0200, Peter Meier wrote: > 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.
This has always been an issue (at least for me). Back in the old days of 2.6.x, I even proposed that instead of deserializing the catalog and serializing it again in a different format for future use, we instead directly dump the serialized version we get from the wire to disk (see #2892 [1]). Of course this would break compatibility with previous versions, but at least we could get rid of this (sometimes) large performance drop. Note that this problem will certainly become much more pregnant if you start to ship your catalogs with file content, instead of using file resources. [1]: https://projects.puppetlabs.com/issues/2892 -- Brice Figureau Follow the latest Puppet Community evolutions on www.planetpuppet.org! -- 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.
