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
<mailto: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
<https://groups.google.com/d/msgid/puppet-users/4d0dc37f-c07e-4f8c-8323-44a90d68b208%40googlegroups.com?utm_medium=email&utm_source=footer>.
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.
