Issue #2892 has been updated by Peter Meier.
Luke Kanies wrote: > I've got a partial branch up. This handles retaining the serialized data all > the way through the request, but it doesn't change anything about how we > cache or whatever. any news on that? what's the work that is left to do? afair the code didn't go over the list and reading the comment of the commit in the branch I assume that the bigger part has yet to be done. ---------------------------------------- Bug #2892: Remove unneeded YAML serialization when caching catalog in puppetd http://projects.reductivelabs.com/issues/2892 Author: Brice Figureau Status: Code Insufficient Priority: Normal Assigned to: Luke Kanies Category: plumbing Target version: Rowlf Affected version: 0.25.1 Keywords: pson json catalog cache serialization Branch: tickets/master/2892 Peter Meier noticed that the puppetd catalog caching was an operation that was taking lots of RAM. Analysis show that for large catalog YAML dumping consumes lots of memory (roughly 3x times the object to serialize). The catalog is sent from the master to the client in serialized format (usually pson/json), the idea would be to directly use it as the local client cache, instead of re-serializing the "live" catalog. The implementation would be: # keep the serialized version of the catalog in the request in the REST client # when caching the catalog, have a specific terminus that would just dump this string to disk -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en.
