Issue #12310 has been updated by R.I. Pienaar.

Ran my manifests with various points in the timelines between 2.7.9 and .10:

<pre>
                 2.7.10                                    42.580
after symb modes 2ac94f94b9af6d8025ee0e771c4c7141ca9705c6  42.236
b4 symb modes    48726b662d2fb5cc3532fca12eb6aa5a3c1622cd  42.197
after facts once c58bfbc64f9f22009cd57c5cc8a924ae21fe3a97  42.448 / 42.496 / 
42.299
b4 facts once    134e826084aa0eec0d065d070288e984a077d21b  36.434 / 36.435 / 
37.633
                 2ca9f9da9baa11e21c58c66820e8ba59e955e7e1  37.129
                 ca7328323ab9de76191601aef373d3d8486c023f  37.873
                 86a806f595f8b7bb280c8c445eef51dfd71bf39d  37.129
after probes     0e4acaf486377cb7741e8cb0cdf96227c449a800  36.192 
before probes    2fd94d2e912a1b0dcc08ff510658948644a7fc1c  33.438
                 2.7.9                                     30.997
</pre>

There's some slow down early on in the series that I will hone into

but it seems I identified the work in #8341 as a posible cause as across the 3 
runs with the before and after hash I can reliably see a significant slow down 
there, will do some more tests 'morow with the early commits to see whats up 
there
----------------------------------------
Bug #12310: Significant slow down in 2.7.10 apply
https://projects.puppetlabs.com/issues/12310

Author: R.I. Pienaar
Status: Unreviewed
Priority: Normal
Assignee: 
Category: 
Target version: 
Affected Puppet version: 
Keywords: 
Branch: 


I've been exploring approaches for running puppet masterless and in the same 
time trying to massage my manifests to be compatible with 2.7.x scoping etc.

I noticed a huge increase in run times between 2.6.9 and 2.7.10 with the same 
manifests, using envpuppet and a git clone I've gathered this information:

<pre>
======== 2.6.9  
notice: Finished catalog run in 9.95 seconds
envpuppet puppet apply --pluginsync    14.45s user 4.99s system 92% cpu 21.098 
total
======== 2.7.9  
notice: Finished catalog run in 16.52 seconds
envpuppet puppet apply --pluginsync    21.92s user 6.90s system 93% cpu 30.814 
total
======== 2.7.10  
notice: Finished catalog run in 21.34 seconds
envpuppet puppet apply --pluginsync    23.58s user 9.42s system 73% cpu 44.662 
total
</pre>

2.7.0 to 2.7.9 performs the same.  While 2.7.0-9 is already a fair bit slower 
than 2.6 was 2.7.10 adds
another 14 seconds to the run using the same manifests on the same machine.

Comparing last_run_summary.yaml files I notice that the big change in run time 
info is service:

<pre>
    2.6.9: service: 2.920294
    2.7.9: service: 8.238562
    2.7.10: service: 12.400952
</pre>

But this does not on it's own account for the time increase there seems to be a 
hit somewhere like state.yaml handling or report handling or something that 
isn't reflected here.

Unsure how to gather more useful information to narrow this down



-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" 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-bugs?hl=en.

Reply via email to