When creating VMs that are on shared storage, preallocate vs dynamic?

Red Squirrel

[H]F Junkie
Joined
Nov 29, 2009
Messages
9,223
Normally I like to create preallocated disks as it supposedly has better performance, and at least I'm using up a chunk of space that is dedicated to that VM, so I don't have to worry about my VMs growing and eating up space over time, they eat it up right away, and don't eat more up from there.

But if the VM is to be stored on remote storage, such as NFS, am I better off to dynamicly allocate the storage or is it still better to preallocate?
 
Yeah..that was quite a post...some of things that I didn't mention were the fact that vSphere would "stun" the VM if it did run out of space and there is a reclaim that you can do manually but I agree, the consensus should be to run thin on the array OR vSphere side, not both. Prior to me leaving my last organization, based on that post you linked I converted my VM's to thick since the storage on the SAN side was already set to thin. I did a storage vMotion to another datastore to accomplish this.
 
Oh yeah thin on thin is silliness... we had that where I used to work and it was a nightmare. You pretty much have to guess how much space you *really* have. If you were to hit the limit, things would get pretty ugly. And of course they filled the SAN right up with tiny drives, instead of putting it half with big drives so it can be expanded. Bad decisions there.

I thick provision my raw storage all the time. I also thick provision my VMs, though I was starting to wonder if performance would be better if it's thin when it's on a network drive. Or does it not matter? I prefer thick just so I can allocate and reserve the space right off the bat. I can fill the drives up with other data if I please without affecting the VMs.
 
Yup, cant remember last time i did a thick provision for a VM. No real reason.
 
Yup, cant remember last time i did a thick provision for a VM. No real reason.

Fault Tolerance & MSCS Cluster Disks :)

But there are valid reasons to do it depending on the scenario. It's all part of the art of design.
 
Oh yeah thin on thin is silliness... we had that where I used to work and it was a nightmare. You pretty much have to guess how much space you *really* have. If you were to hit the limit, things would get pretty ugly. And of course they filled the SAN right up with tiny drives, instead of putting it half with big drives so it can be expanded. Bad decisions there.

I thick provision my raw storage all the time. I also thick provision my VMs, though I was starting to wonder if performance would be better if it's thin when it's on a network drive. Or does it not matter? I prefer thick just so I can allocate and reserve the space right off the bat. I can fill the drives up with other data if I please without affecting the VMs.

Thin on thin is a nogo. I think it has already been pointed out in another topic. We recently had a customer with performance issues on a VNX. Turned out to be the thin/thin.
 
I'm actually using Virtual Box right now. But if there's not really a difference then I'll stick to thick. I like it better for organization purposes mostly.
 
Back
Top