24-10-2019, 01:25 PM
I've got the Vitual Machines working OK so I thought I 'd try compiling the same Xilinx job that I've been using for experiments. It took 48 minutes on my main PC under 64 bit W7. I think I've already said I was astonished when on the same PC it took 25 minutes in a 32 bit XP VM. I've jst run it on my Linux testbed PC which is about 30% as powerful (using Passmark CPU comparison) as my main PC. It took 40 minutes! In other words on a physical PC that's 3 times slower than my main PC, running in a VM, it still beats running native on my main PC.
I must try it on my old main PC which runs XP 32 bit. It's nominally about the same speed as my Linux testbed PC.
I suppose I ought to allow for the effects of SSD versus spinning rust HDDs. On Linux testbed eveything is on SSD at the moment. On main PC the OS and programs are on SSD, data is on HDD. Virtualbox is on the SSD but the VMs are on the HDD, not the SSD. While quite a few files are used while compiling a job I think the really heavy duty stuff is purely executing in RAM. My main PC has enough RAM that it's unlikely to be paging to disk.
I must try it on my old main PC which runs XP 32 bit. It's nominally about the same speed as my Linux testbed PC.
I suppose I ought to allow for the effects of SSD versus spinning rust HDDs. On Linux testbed eveything is on SSD at the moment. On main PC the OS and programs are on SSD, data is on HDD. Virtualbox is on the SSD but the VMs are on the HDD, not the SSD. While quite a few files are used while compiling a job I think the really heavy duty stuff is purely executing in RAM. My main PC has enough RAM that it's unlikely to be paging to disk.
www.borinsky.co.uk Jeffrey Borinsky www.becg.tv
