for posterity - a new puppetlabs ticket was created for this,
https://tickets.puppetlabs.com/browse/PUP-5380, where the root cause of the
problem is pinpointed.
On Tue, Oct 13, 2015 at 3:34 PM, Adam Winberg
wrote:
> ok, so I have been tinkering a bit more with this and I my problems start
> when
ok, so I have been tinkering a bit more with this and I my problems start
when I upgrade to puppet 3.7.5. So 3.7.4 works fine, but 3.7.5 and 3.8.x is
showing some really terrible performance for me.
Running puppetserver (jvm) with 3.7.4, 9 jruby instances and 12G Xmx I get
really good performa
I actually tried the --profile option but never got it to actually record
any 'PROFILE' log data. The logdest and debug flags works as expected, but
no 'PROFILE' entries in the logfile.
On Thu, Sep 17, 2015 at 1:02 AM, Josh Cooper wrote:
> Hi Adam,
>
> On Wed, Sep 16, 2015 at 3:47 AM, Adam Winbe
Hi Adam,
On Wed, Sep 16, 2015 at 3:47 AM, Adam Winberg
wrote:
> Upgraded from 3.7.3 to 3.8.2 and have after that had very slow compilation
> and file serving from the puppet master. We're running our puppetmaster
> with apache/passenger, ca. 900 hosts. Complete puppet runs earlier took
> 10-15s
Upgraded from 3.7.3 to 3.8.2 and have after that had very slow compilation
and file serving from the puppet master. We're running our puppetmaster
with apache/passenger, ca. 900 hosts. Complete puppet runs earlier took
10-15s and after update take 30-300s. Very unstable performance.
Even running w
