One of or customers has a MySQl back end as part of their solution.
They have configured it to have a common master database and a specific slave database per client (they have 10+ slaves). They are using MySQL proxy for this.
They are facing some performance issues including database inserts/updates being queued and taking quite some time to write to the slave databases.
Can you suggest how this can be improved? Are there tools that can be used to help identify where the problems are? Does this seem like a standard approach to you (common master with client specific slaves controlled via MySQL proxy)?
Any advice would be appreciated.
Thanks,
Andy