On Mon, Mar 16, 2009 at 08:54:45AM -0700, Mark Plaksin wrote: > 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.
WAG: are you using MyISAM? Perhaps the global taable lock is biting you with all those UPDATEs. Try using InnoDB (or PostgreSQL) instead. -- Jos Backus jos at catnook.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
