Here at Claranet France, when we've switched to Puppet4, we've made
several mistake
First, the environment cache wasn't enable, and the performance with
Puppet4 is very bad when it's not.
Second, when we've reached 3000 nodes (we have 4 master nodes, 48 core,
64GB, behind 2 HaProxy) the catalog application (not compute) became
slow and slower. we tried to increase the number of JRuby instances from
4 (max in auto mode) to 12 but we had very high load and crashes. The
problem is that the JVM memory is shared between all JRuby Instance, so
just increase th xmx/xms to 1GB per JRuby instance seems to have
resolved all our performance problem.
Now our catalog application time is about 50% faster than on our old
Puppet3 infrastructures (we've also switch all our agent to Puppet4).
Best regards,
Le 11/02/2018 à 02:39, Ramin K a écrit :
tos 6 running Puppet 3.8.x. Ruby 1.8.7 so no http multiplexing. 50% of
agents on Centos 7 w/
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/e6229fd1-1486-9619-9bd5-dfa001f545c6%40quake.fr.
For more options, visit https://groups.google.com/d/optout.
