On Mar 10, 2:49 am, James Turnbull <[email protected]> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> All
>
> Puppet 0.24.8 Release Candidate 1 is now available for testing.
Cool!
The Red Hat spec file makes the RPMs require ruby-augeas. How about
making that optional via --without as follows?
%define with_augeas %{?_without_augeas: 0} %{?!_without_augeas: 1}
%if %{with_augeas}
Requires: ruby-augeas
%endif
> Enhancements to file serving, module and stored configuration
> performance
Even with these fixes we can't run storeconfigs. mysqld eats up all
of our CPUs. Is there some recommended mysql tuning that we should
do? We're far from MySQL experts. FWIW, we turned on query logging
and there are 17k lines in the log associated with a single host.
About half are SELECTs and the other half UPDATEs. We have about 400
hosts and, according to our stats based on puppet reports, we have
about 1.5 million resources total.
How about making some options for storeconfigs? That could help with
performance. We'd be happy if we just had fact names and values for
all of our hosts in the database.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
