Matthew Dickinson
2013-Jul-09 13:51 UTC
[Puppet Users] slow catalog runs after upgrade from 2.7.18 to 3.2.1
Hi, i''ve just upgraded my infrastructure to 3.2.1 - had the puppet master (via mod_passenger) running on 3.2.1 and after a month of stability, upgraded the clients from 2.7.18 I noticed this across the board - the runtime on the client side has increased by approx 50% immediately following the upgrade. My impressions from reading release notes, etc was that it was meant to be 50% faster, not 50% slower? Is this behavior to be expected, or have I missed something? Thanks, see below for log entries: (you can tell where the upgrade happens in the middle) Jul 8 20:01:46 testhost puppet-agent[23393]: Finished catalog run in 17.72 seconds Jul 8 20:11:51 testhost puppet-agent[23393]: Finished catalog run in 17.67 seconds Jul 8 20:21:57 testhost puppet-agent[23393]: Finished catalog run in 18.16 seconds Jul 8 20:32:01 testhost puppet-agent[23393]: Finished catalog run in 17.41 seconds Jul 8 20:42:07 testhost puppet-agent[23393]: Finished catalog run in 17.90 seconds Jul 8 20:52:11 testhost puppet-agent[23393]: Finished catalog run in 17.04 seconds Jul 8 21:02:16 testhost puppet-agent[23393]: Finished catalog run in 17.30 seconds Jul 8 21:09:24 testhost puppet-agent[9142]: Finished catalog run in 25.07 seconds Jul 8 21:19:24 testhost puppet-agent[10921]: Finished catalog run in 24.56 seconds Jul 8 21:29:25 testhost puppet-agent[12662]: Finished catalog run in 26.50 seconds Jul 8 21:39:24 testhost puppet-agent[14316]: Finished catalog run in 24.97 seconds Jul 8 21:49:24 testhost puppet-agent[16296]: Finished catalog run in 24.80 seconds Jul 8 21:59:23 testhost puppet-agent[18203]: Finished catalog run in 24.19 seconds Jul 8 22:09:24 testhost puppet-agent[19686]: Finished catalog run in 25.01 seconds Notice: Finished catalog run in 24.30 seconds Changes: Total: 1 Events: Total: 1 Success: 1 Resources: Changed: 1 Out of sync: 1 Total: 1846 Skipped: 6 Time: Filebucket: 0.00 Group: 0.00 Network config: 0.00 Mount: 0.00 Ssh authorized key: 0.00 Yumrepo: 0.01 User: 0.04 Network interface: 0.06 Exec: 0.25 Package: 0.60 Last run: 1373377650 Total: 14.26 Service: 2.63 Config retrieval: 4.92 File: 5.75 Version: Config: 1373374212 Puppet: 3.2.1 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Matthew Dickinson
2013-Jul-09 13:56 UTC
[Puppet Users] Re: slow catalog runs after upgrade from 2.7.18 to 3.2.1
at the risk of replying to myself, here''s an example from another host - runs now take ~2.5 times as long to complete. Jul 8 20:22:24 testhost puppet-agent[14221]: Finished catalog run in 4.93 seconds Jul 8 20:32:25 testhost puppet-agent[14221]: Finished catalog run in 4.72 seconds Jul 8 20:42:26 testhost puppet-agent[14221]: Finished catalog run in 4.94 seconds Jul 8 20:52:27 testhost puppet-agent[14221]: Finished catalog run in 4.99 seconds Jul 8 21:03:34 testhost puppet-agent[28686]: Finished catalog run in 11.26 seconds Jul 8 21:13:30 testhost puppet-agent[29718]: Finished catalog run in 11.21 seconds Jul 8 21:23:30 testhost puppet-agent[30683]: Finished catalog run in 11.43 seconds Jul 8 21:33:31 testhost puppet-agent[31632]: Finished catalog run in 12.52 seconds FWIW, this in on RHEL6.4 On Tuesday, July 9, 2013 8:51:49 AM UTC-5, Matthew Dickinson wrote:> > Hi, > > i''ve just upgraded my infrastructure to 3.2.1 - had the puppet master (via > mod_passenger) running on 3.2.1 and after a month of stability, upgraded > the clients from 2.7.18 > > I noticed this across the board - the runtime on the client side has > increased by approx 50% immediately following the upgrade. > > My impressions from reading release notes, etc was that it was meant to be > 50% faster, not 50% slower? Is this behavior to be expected, or have I > missed something? > > Thanks, > > > see below for log entries: > > (you can tell where the upgrade happens in the middle) > > Jul 8 20:01:46 testhost puppet-agent[23393]: Finished catalog run in > 17.72 seconds > Jul 8 20:11:51 testhost puppet-agent[23393]: Finished catalog run in > 17.67 seconds > Jul 8 20:21:57 testhost puppet-agent[23393]: Finished catalog run in > 18.16 seconds > Jul 8 20:32:01 testhost puppet-agent[23393]: Finished catalog run in > 17.41 seconds > Jul 8 20:42:07 testhost puppet-agent[23393]: Finished catalog run in > 17.90 seconds > Jul 8 20:52:11 testhost puppet-agent[23393]: Finished catalog run in > 17.04 seconds > Jul 8 21:02:16 testhost puppet-agent[23393]: Finished catalog run in > 17.30 seconds > Jul 8 21:09:24 testhost puppet-agent[9142]: Finished catalog run in 25.07 > seconds > Jul 8 21:19:24 testhost puppet-agent[10921]: Finished catalog run in > 24.56 seconds > Jul 8 21:29:25 testhost puppet-agent[12662]: Finished catalog run in > 26.50 seconds > Jul 8 21:39:24 testhost puppet-agent[14316]: Finished catalog run in > 24.97 seconds > Jul 8 21:49:24 testhost puppet-agent[16296]: Finished catalog run in > 24.80 seconds > Jul 8 21:59:23 testhost puppet-agent[18203]: Finished catalog run in > 24.19 seconds > Jul 8 22:09:24 testhost puppet-agent[19686]: Finished catalog run in > 25.01 seconds > > Notice: Finished catalog run in 24.30 seconds > Changes: > Total: 1 > Events: > Total: 1 > Success: 1 > Resources: > Changed: 1 > Out of sync: 1 > Total: 1846 > Skipped: 6 > Time: > Filebucket: 0.00 > Group: 0.00 > Network config: 0.00 > Mount: 0.00 > Ssh authorized key: 0.00 > Yumrepo: 0.01 > User: 0.04 > Network interface: 0.06 > Exec: 0.25 > Package: 0.60 > Last run: 1373377650 > Total: 14.26 > Service: 2.63 > Config retrieval: 4.92 > File: 5.75 > Version: > Config: 1373374212 > Puppet: 3.2.1 > > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.