Re: [Puppet Users] puppet5 upgrade performance issues

[Chris Smith]

On 11/01/18 09:42, Poil wrote:
> Hey,
> 
> Are you sure that you have environment cache enabled on your Puppet5
> installation ? (because x10 is what we have here when we disable it)

No, that's not enabled at the moment (it wasn't before either). I'm
working on setting that up, I did a test run and it helped quite a bit.

Thanks for the suggestion.

Cheers,
Chris.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/8b8cc991-165b-20df-dbf2-8fe9e48ecd24%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet5 upgrade performance issues

[Chris Smith]

On 11/01/18 08:41, Matthaus Owens wrote:
> Chris,
> 
> Good to know that PuppetDB isn't the cause here. One thing worth doing
> on your servers is moving forward to Puppet-agent 5.3.2. There was a
> performance regression in Puppet 5
> https://tickets.puppetlabs.com/browse/PUP-8009 around
> internationalization and modules (something like 30% in some cases).
> You might also need to set `disable_i18n=true` in the [master] section
> of your puppet.conf.

Nice find, thanks for that.

> To see what puppetserver is doing and how long it takes you can set
> `profile=true` in the [master] section of puppet.conf (I would
> recommend only doing this on one of your servers, as it will generate
> a lot of log output per puppet run). The profiling results will be
> logged at the info level to
> /var/log/puppetlabs/puppetserver/puppetserver.log, so you could then
> inspect the timing of different parts of the agent lifecycle.

Awesome, thanks - I'll give that a shot.

Cheers,
Chris.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/d36ae53a-3692-48f6-8f26-e64bf6fb7091%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet5 upgrade performance issues

[Poil]

Hey,

Are you sure that you have environment cache enabled on your Puppet5 
installation ? (because x10 is what we have here when we disable it)


ref. https://www.example42.com/2017/03/27/environment_caching/

Best regards,

Le 09/01/2018 à 04:31, chris smith a écrit :

Hi there,

I recently did an upgrade from puppetserver 2.7.2 to puppetserver 5.0 
and performance has bottomed out pretty terribly. Agents and puppetdb 
also got updated. Compiling the catalog on the server used to take 
10-20 seconds, now they are taking 90-150 seconds and agent runs are 
taking 30+ minutes (used to be a couple of minutes).


The architecture is distributed, with:
 * a central ca, running puppetserver, puppetdb, postgres 9.6
 * separate puppetservers replicated in other datacentres. These are 
also running puppetdb, pointing writes to the central ca, but reads go 
to a locally replicated database


Other servers (agents) point to the replicated puppetservers to do all 
of the work.


The puppetservers were tuned (upped jvm memory, set max-instances).

The architecture hasn't changed since the upgrade.

The puppetservers are still running hiera3 configs, they haven't been 
converted yet (it's on the list, but from what I read it wasn't a 
showstopper). We have a reasonable amount of encrypted yaml files 
(using hiera-eyaml-gpg), though this was the same as pre-upgrade and 
hasn't changed significantly.


Since the upgrade, I've tried re-tuning the jvm settings, changing 
max-instances and not having much luck at all. I found the 
experimental dashboard on the puppetservers and they show that there 
are no free jruby's, but there has to be something I'm missing that's 
causing that to happen.


I'm lost on what to look at next, is there an easy way to peak inside 
jruby to see what's taking so long?


Any suggestions would be great.

Cheers,
Chris.

--
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+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/4d0dc37f-c07e-4f8c-8323-44a90d68b208%40googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.



--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/b90ba6c6-d3fa-dcff-dfe9-aac05523c01d%40quake.fr.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet5 upgrade performance issues

[Matthaus Owens]

Chris,

Good to know that PuppetDB isn't the cause here. One thing worth doing
on your servers is moving forward to Puppet-agent 5.3.2. There was a
performance regression in Puppet 5
https://tickets.puppetlabs.com/browse/PUP-8009 around
internationalization and modules (something like 30% in some cases).
You might also need to set `disable_i18n=true` in the [master] section
of your puppet.conf.
To see what puppetserver is doing and how long it takes you can set
`profile=true` in the [master] section of puppet.conf (I would
recommend only doing this on one of your servers, as it will generate
a lot of log output per puppet run). The profiling results will be
logged at the info level to
/var/log/puppetlabs/puppetserver/puppetserver.log, so you could then
inspect the timing of different parts of the agent lifecycle.

On Tue, Jan 9, 2018 at 7:11 PM, Chris Smith  wrote:
> Hi,
>
> Thanks for your help.
>
> On 10/01/18 06:36, Matthaus Owens wrote:
>> Chris,
>> To better help you, it would be great to know a few more things about
>> your installation. First question: are you running puppetserver 5.0.0
>> or something later in the 5.x series (and is it the same on all
>> servers)? Second, what version of the puppet-agent are on those
>> servers? puppetserver 5.1.3 included a fix for
>> https://tickets.puppetlabs.com/browse/SERVER-1922 which should improve
>> performance some.
>
> Hm. Interesting, thanks. I'll check out what a 5.0 -> 5.1 upgrade will do.
>
>>
>> Hiera 3 + hiera-eyaml may also be contributing to the slowness. Here
>> is one ticket (related to SERVER-1922) that indicated moving to hiera
>> 5 improved compile times substantially:
>> https://tickets.puppetlabs.com/browse/SERVER-1919
>
> Also interesting but as noted on the last comment, a lot of the
> structure was changed so that might not all have been hiera3 -> hiera5.
>
>> To dig into what may be causing the compiles to be slower, I would
>> recommend first checking out the client metrics.
>> https://puppet.com/docs/puppetserver/5.1/http_client_metrics.html has
>> some details, and I would be interested in the client metrics that
>> page lists under the /puppet/v3/catalog. They are PuppetDB related
>> requests, and as that was also upgraded alongside puppetserver it
>> would be good to eliminate PuppetDB as a contributor. PuppetDB
>> slowness can show up as slow catalog compiles, which in turn will hold
>> jrubies for longer and might explain some of what you are seeing.
>
> puppetservers are all the same.
>
> We upgraded to:
> # /opt/puppetlabs/server/bin/puppetserver -v
> puppetserver version: 5.0.0
>
> puppetdb is this, it should have been 5.0 as well but I stuffed it up.
> # /opt/puppetlabs/server/bin/puppetdb -v
> puppetdb version: 5.1.3
>
>
> agents are all:
> # /opt/puppetlabs/puppet/bin/puppet --version
> 5.0.0
>
>
> The metrics say
>
> {
>   "route-id": "puppet-v3-file_metadata-/*/",
>   "count": 9373,
>   "mean": 10217,
>   "aggregate": 95763941
> },
> {
>   "route-id": "puppet-v3-catalog-/*/",
>   "count": 828,
>   "mean": 94773,
>   "aggregate": 78472044
> },
> {
>   "route-id": "puppet-v3-node-/*/",
>   "count": 831,
>   "mean": 62709,
>   "aggregate": 5279
> },
> {
>   "route-id": "puppet-v3-file_metadatas-/*/",
>   "count": 4714,
>   "mean": 9288,
>   "aggregate": 43783632
> },
> {
>   "route-id": "puppet-v3-report-/*/",
>   "count": 780,
>   "mean": 3433,
>   "aggregate": 2677740
> },
>
>
>
>   "http-client-metrics": [
> {
>   "count": 821,
>   "mean": 48,
>   "aggregate": 39408,
>   "metric-name":
> "puppetlabs.localhost.http-client.experimental.with-metric-id.puppetdb.command.replace_catalog.full-response",
>   "metric-id": [
> "puppetdb",
> "command",
> "replace_catalog"
>   ]
> },
> {
>   "count": 832,
>   "mean": 25,
>   "aggregate": 20800,
>   "metric-name":
> "puppetlabs.localhost.http-client.experimental.with-metric-id.puppetdb.command.replace_facts.full-response",
>   "metric-id": [
> "puppetdb",
> "command",
> "replace_facts"
>   ]
> },
> {
>   "count": 780,
>   "mean": 19,
>   "aggregate": 14820,
>   "metric-name":
> "puppetlabs.localhost.http-client.experimental.with-metric-id.puppetdb.command.store_report.full-response",
>   "metric-id": [
> "puppetdb",
> "command",
> "store_report"
>   ]
> },
> {
>   "count": 215,
>   "mean": 43,
>   "aggregate": 9245,
>   "metric-name":
>