[Fed-Talk] Re: Performance hit with Parallels inside of FileVault
[Fed-Talk] Re: Performance hit with Parallels inside of FileVault
- Subject: [Fed-Talk] Re: Performance hit with Parallels inside of FileVault
- From: "Shawn A. Geddis" <email@hidden>
- Date: Mon, 10 Dec 2007 22:19:00 -0500
On Dec 10, 2007, at 7:30 PM, David Emery wrote:
Tiger experience: I've noticed a big performance hit whenever I
launch Parallels from my FileVault account, often taking 10 minutes
to load. What I suspect is that Parallels is putting its files
somewhere in ~, even though I told it not to do that...
Here's an experiment: Tell Parallels (both app preferences and the
specific VM) to put the data into somewhere outside of the Vault.
(I use /Users/Shared/Parallels-VM, and I'm OK with that since I -
never- keep any proprietary/sensitive data on Windows :-). I bet
this'll help performance, and maybe make the freeze go away. Try
that and let us know how it works out...
Folks should keep in mind that when using *Environments* that store
data inside a "container" (disk image) that is then stored inside
another disk image, your performance will be adversely impacted by
*storage expansion*.
Walk thru this with me.....
(1) You are running Mac OS X while accessing your FileVault Account --
which is an encrypted disk image
(2) You have installed Parallels -- which uses disk images for
"containers"
(3) You Launch Parallels -- which opens the image file and mounts the
disk image as a volume
(4) Windows needs to grow the space for various reasons (fill in with
item of your choice)
(a) Windows requests more space on disk, but disk image has reached
its size limit
(b) Parallels requests more space on disk, but disk image has
reached its size limit
(c) FileVault needs more space via sparse disk image, but disk
image reached its size limit
(d) Mac OS X expands the Sparse Disk Image with encrypted chunk
(e) FileVault now has expanded by small chunk of space to
accommodate additional file(s)
(f) Parallels now has expanded by small chunk of space to
accommodate additional file(s)
(g) Window's available storage expanded by small chunk of space to
accommodate additional file(s)
(h) Windows wants to install more files or expand existing files
beyond current size...
(a) Windows requests more space on disk, but disk image has reached
its size limit
(b) Parallels requests more space on disk, but disk image has
reached its size limit
(c) FileVault needs more space via sparse disk image, but disk
image reached its size limit
... rinse and repeat....
This is why you are seeing a big performance hit whenever launching
Parallels from a FileVault Account.
There is of course a rub between the different OS environments and how
space is allocated and managed.
- Shawn
_____________________________________________________
Shawn Geddis Security Consulting Engineer Apple Enterprise
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Fed-talk mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden