List:General Discussion« Previous MessageNext Message »
From:Johan De Meersman Date:March 4 2011 11:21am
Subject:Re: best practice: mysql_multi, VMs w/single instance per or doesn't matter?
View as plain text  
Other people have answered with pros and cons of virtualisation, but I would rather ask
another question: why do you feel it necessary to split up the database?

If it's only used for QC, it's probably not in intensive use. Why would you go through the
bother of splitting it up? You're staying on the same server, apparently, so you'll have
to decide which instance gets what part of cpu, memory and other resources, you'll have
to provide separate backup for all instances, et cetera; while leaving things as they are
is zero effort.

What is the problem with the current setup that will be resolved by splitting?


-- 
Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt, is ras een ezel
Thread
best practice: mysql_multi, VMs w/single instance per or doesn't matter?Sid Lane3 Mar
  • Re: best practice: mysql_multi, VMs w/single instance per or doesn'tmatter?Reindl Harald3 Mar
    • Re: best practice: mysql_multi, VMs w/single instance per or doesn't matter?Claudio Nanni3 Mar
      • RE: best practice: mysql_multi, VMs w/single instance per or doesn't matter?Daevid Vincent4 Mar
  • Re: best practice: mysql_multi, VMs w/single instance per or doesn't matter?Johan De Meersman4 Mar
    • RE: best practice: mysql_multi, VMs w/single instance per or doesn't matter?Jerry Schwartz4 Mar