I figured there would be no clearcut answer. I was curious if there were any nuggets of
wisdom or rules of thumb I was overlooking.
We initially launched sharing db servers, but had performance trouble. We've since tracked
down problems in our app server config (WordPress does not like to share an app server)
and added memcache. So I think we're ripe for another try.
On Oct 18, 2011, at 5:39 PM, Lydia Rowe wrote:
> You have answered your own question, good sir. Or so I have come to believe. Is your
> primary concern $? Is your organization focused on the bottom line? Option B allows you to
> move in the costsaving direction. I imagine some may object to sharing resources between
> (potentially exploitable) WordPress installations but hey, so goes the show, as they say
> around these parts here!
> On Oct 18, 2011 5:19 PM, "Mark, Ryan" <rmark@stripped> wrote:
> Architecture question I'm having trouble finding an answer to:
> I run four WordPress websites. I have mysql setup in a write master/read replica
> slave configuration on Amazon. There is one master that all the WordPress instances write
> to. I'm trying to figure out how to setup the read replicas.
> Should I:
> A. Give each WordPress instance it's own read replica?
> B. Have all the WordPress instances use all the read replicas?
> I have done A before, and it works fine. But by going with B I can consolidate, use
> beefier hardware and save money.
> Any thoughts?
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=1