On Nov 13, 2012, at 7:35 AM, David Schmitt <[email protected]> wrote: > On 12.11.2012 14:34, Brice Figureau wrote: >> On Mon, 2012-11-12 at 13:06 +0100, David Schmitt wrote: >>> Hi, >>> >>> I've just upgraded my local test master to 3.0 and wanted to share the ups >>> and downs. >>> >>> * The upgrade went as smooth as could be expected: config.ru migration >>> tripped me up, but was documented. >>> * There were still unexpected differences in behaviour which were not >>> warned by 2.7. In my case I was inspecting variables in templates and in >>> 3.0 scope.lookupvar now returns nil in some cases. >>> * Compilation times for my biggest testcase (~3000 collected resources) >>> dropped from ~110 seconds to ~70 seconds. >>> * Agent runtime sadly did not improve beyond this: >>> Nov 12 12:43:31 inhas60228 puppet-master[23884]: Compiled catalog for >>> inhas60228.eu.boehringer.com in environment david in 78.16 seconds >>> [...] >>> Nov 12 12:46:58 inhas60228 puppet-agent[32596]: Caching catalog for >>> inhas60228.eu.boehringer.com >>> Nov 12 12:47:36 inhas60228 puppet-agent[32596]: Applying configuration >>> version '1352720534' >>> [...] >>> Nov 12 12:49:47 inhas60228 puppet-agent[32596]: Finished catalog run >>> in 131.95 seconds >> >> Well, apparently caching catalog is taking around 38 seconds, which >> should be compared to what it took beforehand (you didn't paste your >> previours catalog run for this host). This time is not accounted in the >> catalog run itself, and I believe that's where the agent is now faster, >> so I don't expect you'll see large catalog run time decrease. >> This catalog run time is mostly driven by the resource you're managing, >> and there's no magical bullet in Puppet 3.0 that automatically make >> calls to the package manager, files, users or services dramatically >> faster... > > The run with 2.7.19 takes around ten minutes wallclock time. 3.0.1 takes > around nine minutes wallclock for a complete "puppet agent --test". The > difference is approximately the time saved on master compiling the catalog. > I'm not concerned about the two minutes spent actually managing 3000 > resources (~0.04s per resource). I'm concerned about the other seven minutes > overhead.
Any idea what that other seven minutes is? That seems completely pathalogical. -- 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 [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.
