On 4/20/17 3:32 AM, Cesar wrote:
I was wondering whether there is any way to reduce catalog compilation?
Could the catalog compilation be split across different Puppet master
processes or something like that?
- upgrade to 3.8.x, definitely performances gains to be had.
- Passenger 5/5.1 and tune for the CPU/workload,
https://ask.puppet.com/question/13433/how-should-i-tune-passenger-to-run-puppet/
- Run Ruby 2.1 on the master. Performance in Ruby 1.8.7 was terrible.
Expect a 30-50% bump for each version you jump from 1.8.7, 1.9.3, 2.0,
and 2.1.
Ruby version is the performance limiter in Puppet 3.x rather than Puppet
3 vs 4 or the app server at least in puppet-server 1.x. It's unfortunate
that *every* benchmark I've seen comparing Puppet 3/Passenger vs Puppet
4/JVM was done with Ruby 1.8.7 including the benchmarks Cern did. IME
running modern Ruby gets you very very close to Puppet server
performance. It also helps you migrate to Puppet 4 if you have custom
functions, types/providers, etc which aren't Ruby 1.9+ ready.
Ramin
--
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/06d7a669-606b-bd55-b01a-56ce954d6f06%40badapple.net.
For more options, visit https://groups.google.com/d/optout.
