[AccessD] William Hindman (Re: Visual Basic 2008 Express&VB.NET)

Stuart McLachlan stuart at lexacorp.com.pg
Sat Mar 14 20:35:23 CDT 2009


Just found out why this was so slow.  

<quote>
For more flexible storage management, use a dynamically expanding image. This will 
initially be very small and not occupy any space for unused virtual disk sectors, but the 
image file will grow every time a disk sector is written to for the first time. While this format 
takes less space initially, the fact that VirtualBox needs to constantly expand the image file 
consumes additional computing resources, so until the disk has fully expanded, write 
operations are slower than with fixed size disks. However, after a dynamic disk has fully 
expanded, the performance penalty for read and write operations is negligible  
</quote>

Correction to my previous advise to  Arthur:
Set up either a dymanic or fixed disk depending on how you are going to using the VM and 
how much space you have available.


(Note to self: RTFM)
-- 
Stuart

On 15 Mar 2009 at 11:12, Stuart McLachlan wrote:

> Here the  XP VM is *much* slower than Native. 
> I suspect that while sequential reads from the Virtual Disk are very efficient, hence the good 
> loading times, random writes would have a lot more overhead.




More information about the AccessD mailing list