On Mon, 2012-05-14 at 15:39 -0700, Luke Kanies wrote: > On May 14, 2012, at 2:22 PM, Nick Lewis wrote: > > > On Monday, May 14, 2012 at 2:19 PM, Trevor Vaughan wrote: > > > Any suggestions on where to benchmark here? I tried to figure out > > > where to hit it but didn't really get anywhere with it. > > > > > > > > > I did try using pure ruby to load the catalog from disk using the > > > Puppet methods and it took 7 seconds in a case where Config > > > retrieval > > > is reporting around 40 seconds. > > > > > > > > The catalog is being serialized or deserialized three times: once to > > PSON on the master to transfer to the agent, once from PSON to > > revive on the agent, and once to YAML for the agent to cache it. > > That seems like it basically ought to account for the extra time, if > > one deserialize was 7 seconds. > > > JSON serialization is a negligible amount of time - most of that is > being eaten up in YAML. > > > 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 -- 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.
