Jira (PUP-10233) environment_classes API endpoint extremely slow
Title: Message Title Maggie Dreyer commented on PUP-10233 Re: environment_classes API endpoint extremely slow Are you still having performance issues around this? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341970.157901085.73548.1604618880175%40Atlassian.JIRA.
Jira (PUP-10233) environment_classes API endpoint extremely slow
Title: Message Title Charlie Sharpsteen commented on PUP-10233 Re: environment_classes API endpoint extremely slow I'm a bit confused by: This spawns 32 jruby processes hitting: /puppet/v3/environment_classes" How exactly is that activity showing up? As far as I know, that API endpoint is only used by external services like the PE Console. Unless I'm missing something, having 32 request roll in for it seems like bad behavior in some external process. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341970.157901085.34750.1599853080085%40Atlassian.JIRA.
Jira (PUP-10233) environment_classes API endpoint extremely slow
Title: Message Title Thomas Hallgren commented on PUP-10233 Re: environment_classes API endpoint extremely slow One option here could be to use a Go puppet parser. It has way better performance than the Ruby parser and would be pretty easy to also make multi-threaded. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341970.157901085.29528.1579462800167%40Atlassian.JIRA.
Jira (PUP-10233) environment_classes API endpoint extremely slow
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10233 environment_classes API endpoint extremely slow Change By: Josh Cooper Team: Froyo Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341970.157901085.27738.1579217520143%40Atlassian.JIRA.
Jira (PUP-10233) environment_classes API endpoint extremely slow
Title: Message Title Jason V Lang created an issue Puppet / PUP-10233 environment_classes API endpoint extremely slow Issue Type: Bug Assignee: Unassigned Created: 2020/01/14 6:07 AM Priority: Minor Reporter: Jason V Lang I've been troubleshooting "performance" issues with puppet when we sync new code (and update the cache via the API) PuppetServer 5.3.1 Tested with Jruby-9k and "normal jruby" as well as compile mode jit and off, with no real difference other than "9k" seems even 30% slower overall Environment, 18,000 Agents, 18 PuppetMasters as configured below, 1 hour check-in time. 32 Environments with approx. 1100 classes per environment PuppetServer Switches/Args Tested: Configuration 1: /usr/bin/java -Xms45G -Xmx45G -XX:+UseTransparentHugePages -XX:+UseLargePagesInMetaspace -XX:+AlwaysPreTouch -Xloggc:/var/log/puppetlabs/puppetserver/puppetjvmgarbagecollect.log -verbose:gc -XX:ReservedCodeCacheSize=768m -XX:MetaspaceSize=4096m -XX:MaxMetaspaceSize=4096m -XX:+UseConcMarkSweepGC -XX:G1HeapRegionSize=8m -Dappdynamics.agent.applicationName=Puppet -Dappdynamics.agent.nodeName=fmnpmprh1.paychex.com -Dappdynamics.agent.tierName=PuppetMaster -Dappdynamics.controller.hostName=appdcontroller.paychex.com -Dappdynamics.controller.port=9998 -Dappdynamics.controller.ssl.enabled=false -Dappdynamics.agent.disable.retransformation=true -Dappdynamics.agent.accountName=customer1 -Dappdynamics.agent.accountAccessKey=SJ5b2m7d1$354 -Dappdynamics.agent.force.agent.registration=true -Dappdynamics.agent.agentRuntimeDir=/opt/product/appdynamics-agent/AppServerAgent -javaagent:/opt/product/appdynamics-agent/AppServerAgent/javaagent.jar -Djava.security.egd=/dev/urandom -XX:_OnOutOfMemoryError_=kill -9 %p -cp /opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar:/opt/puppetlabs/server/apps/puppetserver/jruby-1_7.jar:/opt/puppetlabs/server/data/puppetserver/jars/* clojure.main -m puppetlabs.trapperkeeper.main --config /etc/puppetlabs/puppetserver/conf.d --bootstrap-config /etc/puppetlabs/puppetserver/services.d/,/opt/puppetlabs/server/apps/puppetserver/config/services.d/ --restart-file /opt/puppetlabs/server/data/puppetserver/restartcounter Configuration 2: /usr/bin/java -Xms62720m
