"J. Roeleveld" <[email protected]> writes: > On November 20, 2016 6:21:40 AM GMT+01:00, Alan McKinnon > <[email protected]> wrote: >>On 20/11/2016 02:59, Harry Putnam wrote: >>> An emerge of webkitgtk-2.14.2 has been running for over 2hrs. I >>> wonder if I am starving my vbox vm of gentoo with 3GB or ram. >>> >>> Top's cpu usage is fluxuating between 45% and 99% during this compile >>> >>> Portage pulling 99% by itself at times. >>> >>> I thought 3GB was a bit high for a vm compared to what I've given >>debian >>> vms... can anyone give some guidance about how much ram to allow a >>> gentoo vm in Vbox? >>> >>> I'm on a windows 10 host with 32 GB ram but running a number of vms. >>> >>> >> >>Depends on what you are compiling. webkitgtk is a brute, so is >>thunderbird, libreoffice and other usual culprits. Those sorts of build >>systems need as much ram as you can spare whereas the rest of the time >>vm itself needs as much as it needs to do whatever it is you want it to >>do. >> >>What hypervisor are you using, and can you use memory ballooning? > > MS Windows desktop OSes are not the best platforms to run multiple VMs on.
I'm just experimenting with several OS's ... The Vbox vms I run for actual work are hosted on Solaris x86 (openindiana) > Also, overcommitting CPUs has a bad influence on performance, > especially if the host wants to use all cores as well. That is what I asked advice about. What do you call `overcommitting'. For example with only 1 Vbox vm started and no serious work being done by the windwos-10 os. On an HP xw8600 with older 2x Xeon 5.60 3.00Ghz with 32 GB ram
