Hello, On 27 April 2012 15:56, Phil Holmes <m...@philholmes.net> wrote:
> > It may depend on your hardware whether this makes sense. My Ubuntu build > box can multithread within the VM, whereas my (older) Windows box can't. Depends on the paravirtualization. eg. http://www.howtogeek.com/howto/linux/linux-tip-how-to-tell-if-your-processor-supports-vt/ Most modern server hardware has 'vt-enabled' CPUs on them (even more recent consumer laptop/desktop hardware). This makes a world of difference to speed and performance. You then need to tick a box more or two to enable that stuff in VBox or KVM. Remember though that LilyDev is 32bit so if you use KVM you must not go over 4096 for your RAM (even if you have more) else, I found, it will just default to 128mb! Vbox is a bit more smart, but you still cannot address more than 4GB of RAM in a 64bit VBox install using LilyDev. So if you have lots of GBs of RAM to play with, from my experience, KVM is much more 'forgiving' in terms of having multiple VMs using more CPUs than you have in reality. Vbox isn't. I haven't used it for a while now but it will stop you allocating more CPUs that you have physically on multiple machines even if in reality one or more VMs are not doing much. KVM will spread the load (so to speak) better and I often forget and run 3 VMs using theoretically using 21 Virtual CPUs! I only notice when I do a make -j7 and am working on one of the other VMs..it does kind of grind to a halt at that point. :) James _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
