Thanks Pablo...
I understand and I will do this !
Best regards,
Wagner.
On 2/18/2011 2:10 PM, Pablo Sanchez wrote:
[ Comments below, in line ]
On Friday 18 February 2011 at 10:59 am, Wagner Alonso penned
about "Re: [VBox-users] Doubt about amount of virtual machines are supported on
Virtual Box !"
For example: I have a machine with solaris installed, this machine
has 20 virtual machines running on virtualbox. What I need to know
is: how much this solaris server needs of resources to run those
virtual machines.
Hi Wagner,
Thank you for the clarification. My last detailed response still
applies however I'm assuming it wasn't clear.
Your problem is a Capacity Planning problem. What you need to figure
out is what types of workloads you'll have in the VM's as well as the
type of O/S you plan on installing. For example, you may have the
following break down:
o 5 VM's running Linux e-mail servers
o 7 VM's running Windows 7, user's surfing and checking e-mail
o etc
Next, for each group, you need to determine how many resources are
needed at /peak/ period. Suppose the e-mail servers typically handle
100 e-mails per hour (super light) but at 2 am, they all get backed
up. The back-up would be a peak period for both CPU and IO.
Once you have peak values per group, you sum those values to size the
Host O/S to ensure the Host O/S can accommodate the VM needs /plus/
its needs - don't forget the Host O/S.
I hope the above is clear. As I said, your issue is a Capacity
Planning problem. You need to know the expected /peak/ demand. You
and/or your customers should know both the expected /peak/ demand.
Now, if it were /me/, I'd set up a VM of each type and install the
customer software and emulate their workload while monitoring the Host
O/S. This would give me hard numbers from which to plan on the Host
O/S. I'd add some extra `fluff' for growth. Ah yes, don't forget
expected growth in your sizing.
Cheers,
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
