Hi there, We've got a puppet (0.24.8) instance with something like a hundred nodes on it. The puppetmaster is running under passenger, we've got both stored configs and dashboard reports going to a MySQL database on the same host. The dashboard itself is now in production use as our external node configuration and reporting tool. Oh yes, we're definitely living the dream.
Our problem is that the dashboard is just getting slower and slower as time goes by, and the database is becoming swamped. It's a concern now that it has become such a key tool. Can anyone enlighten me as to whether there is any housekeeping that can be done to the dashboard database, in order to make the application any faster? Are old reports purged at any time, or will they hang about for ever? Our dashboard_production.reports table now contains ~380,000 entries and consumes 814MB of disk space. Would it help to prune these to a certain time-period? Might there be any indexes missing from my database? I think I installed the dashboard at version 1.0, but ran the database upgrade script between 1.0.1 and 1.0.3. I'm doing incremental MySQL tuning anyway, but I'd like to know if anyone else has any suggestions or similar experiences. Thanks. -- Ben Tullis -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
