After my last article VMware View 5.0 3D Reverse Engineered I received couple emails asking for the video .vswp sizes based on resolution and number of displays, rather than amount of video RAM assigned to the virtual desktop.
VMware View has always allowed administrators to select the number of displays and the resolution to be utilized in a desktop pool. With VMware View 5.0 administrators still select resolution and number of displays, however only if 3D is not used.
With 3D enabled VMware View 5.0 will ask for the amount of RAM to be assigned to video. I depicted in the table below how memory overhead changes according to amount of video RAM select. The table below identify video RAM with 8, 16, 64 and 128 MB. On the leftmost column there is the amount of video swap created. If you don’t know about the secondary .vswp file created by vSphere 5.0 please read vSphere 5.0 New .vswp file & Storage Tax on VDI.
3D is not often in use, and administrators still want to know how much storage will be utilized by the video .vswp file based on resolution and number of displays. The table I created below identifies in MB the amount of storage used by the .vswp for each resolution and number of displays.
As you will notice, the minimum .vswp is 49MB and the maximum is 104MB. (This does not include 3D). Just out of curiosity, 104MB .vswp file equals to an assigned video ram of 128MB.
When 3D is enabled a 256MB overhead is added to the secondary .vswp file. Therefore, if you are planning to use 3D you should size datastores appropriately to accommodate the difference. This additional 256MB help virtual machines not to run into performance issues when executing 3D display operations. The 256MB overhead is independent of how much vRAM you assigned in VMware View 5.0.
The table below gives you in MB the amount of storage utilized:
Now, all this can be very complex and if you have any questions please ask. However, I wanted to make it easier and I am adding all this calculation into my online VDI calculator http://myvirtualcloud.net/?page_id=1076.