That ticket (#2892) is about the amount of memory being used during conversion. Is that still the problem? Or is the problem really now centered around the amount of time that the conversion is taking? Either way using JSON all the way through would probably fix both problems.
On May 15, 2012, at 1:17 AM, Brice Figureau wrote: > On Tue, 2012-05-15 at 00:43 -0700, James Turnbull wrote: >>>> Just getting rid of that yaml serialization -- or switching to JSON -- >>>> would make a huge difference. >>>> >>> >>> I'll sound like a broken record, but that'd be awesome if we could >>> resurrect #2892 from the grave: >>> https://projects.puppetlabs.com/issues/2892 >>> >> >> Didn't that get supplanted by: >> >> https://projects.puppetlabs.com/issues/3714 >> > > It's additional: caching in JSON is good because it's faster. > I still think we don't need to re-serialize what we already have > serialized, so we'd gain a serialization in the cycle (ie 1/3 of the > total time retrieving the catalog), hence my request of resurrecting > #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. > -- 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.
