On Mon, 2009-03-16 at 08:54 -0700, Mark Plaksin wrote: > 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.
Did you use the whole 0.24.8RC1 or only the aforementioned patch? > mysqld eats up all > of our CPUs. Is there some recommended mysql tuning that we should > do? We're far from MySQL experts. Here are several general tips: * use InnoDB for better concurrency, and data persistance * use a recent mysql version (ie 5.0 or 5.1) * properly size your innodb_buffer_pool to the rough size of your on-disk database to not be I/O bound * use a dedicated server for mysql (and not a VM or the same host as your master). Use decent hardware. * put your databases files on a RAID10 (or RAID1) with Battery Backed Cache (that's actually really important to absorb the fsyncs without being detrimental to the performance) * use as more spindles as you can for better concurrency > FWIW, we turned on query logging > and there are 17k lines in the log associated with a single host. Which is not normal. With the perf path I contributed, you should see at most for one host, if nothing has changed: * 1 SELECT request for the querying the host * n SELECT request for exported resources (n == the number of exported resources) * a few request to get the facts * 1 SELECT request to retrieve parameters * 1 SELECT request to retrieve tags * a few update If you made changes to the manifests, then that's normal to see more insert requests. > 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. You can select count(*) from resources group by host_id to get the number of resources per host. On which tables do you see the UPDATES? I'd be interested in helping diagnose the issue (and/or provide any possible fix), feel free to contact me privately or on #puppet (I'm masterzen) if you want to discuss this. -- Brice Figureau My Blog: http://www.masterzen.fr/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
