You might need to increase the Java Virtual Machine (JVM) memory allocated to Java services or ActiveMQ to improve performance in your Puppet Enterprise (PE) deployment.
pe.conf
only — not the console — to specify
configuration parameters. Using pe.conf
or Hiera ensures that configuration is applied to both
your master and replica. Increase the Java heap size for PE Java services
The Java heap size is the Java Virtual Machine (JVM) memory allocated to Java services in Puppet Enterprise (PE). You can use any configuration method you choose. We will use the console to change the Java heap size for console services, Puppet Server, orchestration services, or PuppetDB in the examples below.
Increase ActiveMQ heap usage (master only)
ActiveMQ uses a default heap size of 512MB, but you can increase this as needed.
- In the console, click PE Infrastructure node group, select the PE ActiveMQ Broker group. , and in the
-
Click Configuration and locate
the
puppet_enterprise::profile::amq::broker
class. -
Click the Parameter name list,
select
heap_mb
, and in the value field, enter 1024. - Click Add Parameter, and commit changes.
-
On the command line on the master, run
puppet agent -t
to start a Puppet run and apply the change.
Disable Java garbage collection logging
Java garbage collection logs can be useful when diagnosing performance issues with JVM-based PE services. Garbage collection logs are enabled by default, and the results are captured in the support script, but you can disable them.
.yaml
file. Add any of the
following parameters as needed:
puppet_enterprise::console_services::enable_gc_logging: false
puppet_enterprise::master::puppetserver::enable_gc_logging: false
puppet_enterprise::profile::orchestrator::enable_gc_logging: false
puppet_enterprise::puppetdb::enable_gc_logging: false
puppet_enterprise::profile::amq::broker::enable_gc_logging: false