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. -- Luke Kanies | http://about.me/lak | http://puppetlabs.com/ | +1-615-594-8199 -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to puppet-dev@googlegroups.com. To unsubscribe from this group, send email to puppet-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
