Pablo,
I think that you didn't understand my question or I didn't explain
properly. :-)
I need know: which consumes the machine that runs the virtual machine.
Consumption of the VirtualBox Server.
But anyway, thanks so much for your explain below.
do you Understand now?
Regards,
Wagner.
On 2/18/2011 12:46 PM, Pablo Sanchez wrote:
[ Comments below, in line ]
On Friday 18 February 2011 at 9:21 am, Wagner Alonso penned
about "Re: [VBox-users] Doubt about amount of virtual machines are supported on
Virtual Box !"
Pablo,
One more question... =)
I would like know, if you know what is percentage I have to reserver
for Solaris Machine running VirtualBox? This means: whats overhead
of solaris machine?
Hi Wagner,
Please feel free to ask as many questions as you like. That's the
purpose of this list. :)
Unfortunately, I cannot answer the above without knowing expected
workload within the VM. Also, I don't run any Solaris VM's so I can't
say how much CPU they consume sitting at `idle' The other variant
will be the speed of your processor(s). You can always use SPECint to
normalize your processor's speed to known values.
If I were in your situation, I'd do something like the following to
come up with a rough idea.
For example, I have an I7 950, hyperthreading disabled. At the
moment, my idle W7 VM is consuming 12-14% of a CPU. It's currently
running my client's VPN software and I have a cygwin window,
port-forwarding to my host. Hardly any `work'
Given the above, I know I can run 28 W7 VM's if they're mostly idle.
:)
100% of a CPU/14% = 7.14
4 CPU's = 4 * 7 = 28
However, I only have 12 GB of RAM. My W7 VM gets 768 MB so my maximum
really is 15 W7 VM's:
12000 MB/768 MB = 15
However, I really should leave some memory for my Host O/S so perhaps
only 14 W7 VM's.
The above doesn't take into account IOPS requirements: how many IOPS
are required at peak? You'll need to ensure your I/O subsystem can
sustain the demand.
HTH.
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
