Issue #7584 has been updated by Daniel Pittman.
Garrett Honeycutt wrote: > Dashboard's mysql configs let you specify a host, but they do not break it up > into a write host and a read host. For further scalability it would be > beneficial to have different read and write handlers for the SQL connections. Hey, cool! How did you figure out that the write load from Dashboard was a performance problem? We are trying to work out how to improve performance, so this way we can leverage your methodology rather than having to redo the same benchmarking, or get access to the same SQL trace and timing logs. :) ---------------------------------------- Feature #7584: ability to designate different read and write hosts for mysql in the Dashboard https://projects.puppetlabs.com/issues/7584 Author: Garrett Honeycutt Status: Unreviewed Priority: Normal Assignee: Category: Target version: Affected Puppet version: Keywords: mysql scalability Branch: Dashboard's mysql configs let you specify a host, but they do not break it up into a write host and a read host. For further scalability it would be beneficial to have different read and write handlers for the SQL connections. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en.
