Sid Lane
>Cc: MySql
>Subject: Re: best practice: mysql_multi, VMs w/single instance per or doesn't
>matter?
>
>
>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
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
se that don't, and those that don't know binary.
> -Original Message-
> From: Claudio Nanni [mailto:claudio.na...@gmail.com]
> Sent: Thursday, March 03, 2011 2:14 PM
> To: Reindl Harald
> Cc: mysql@lists.mysql.com
> Subject: Re: best practice: mysql_multi, VMs
Just know that there is not-a-problem in running multiple instances on the
same host,
then all you have to do is to evaluate the performance factor.
In your case I would not introduce the overhead of the VMs,
but take advantage of this to learn how to manage multiple instances on the
same host that
i would use virtual machines because port/socket/configuration
after running our whole infrastructure on vmware i can not understand
how i could live without machine-snapshots and auto-failover :-)
on hardware with virtualization support performance is also
not a problem and ESXi is free without
I've always had a single physical server that is the qc mysql database for
all our applications but it's now up to 85 schemas so I want to break it up
along the same lines as production (where there's redundant pools of mysql
servers by application class).
my basic question is whether it's better
