Posts

Showing posts with the label compression

VMware vSphere 7.0 Update 1 & vSAN 7.0 Update 1

Right before VMworld, VMware has announcement some new releases. Two of which that has lots of new stuff to look forward to is vSphere and vSAN. Here I am going to list down all the resources that you can read or watch to find out more on what is new in both vSphere 7.0 Update 1 and vSAN 7.0 Update 1. vSphere 7.0 Update 1 Check out the announcement  here  and the youtube video  here . AMD SEV-ES Support in vSphere 7 vSphere With Tanzu - Networking with vSphere Distributed Switch vSphere 7 Update 1 – AMD SEV-ES   AMD SEV-ES Support in vSphere 7 ( video ) vSphere Clustering Service (vCLS) (updated) vSphere Lifecycle Manager Improvements (updated) Unprecedented Scalability (updated) As usual, with almost in every release, you see the maximum supported numbers goes up. However, one of the key supported on CPU security is from AMD on SEV-ES. Check out the article  here . vSAN 7.0 Update 1 Check out the announcement  here  and video . Duncan Epping have ...

VMware Horizon Mirage Performance Catcha

Image
It has been some time since my last post.  Have been really busy however I always make a point to at least do a meaningful post a month.  Since VMworld is also round the corner, there will be many updates from all other bloggers around the world. Recently was doing a Proof of Concept (POC) for Horizon Mirage and was questioned on the time to centralize an end device was too long. Here's what happen: A simple centralize of endpoint took as long as 140mins in one setup and 52mins in another which could not have been shorter since the endpoint is plain OS image about 40GB in size. Setup 1 First setup that took 140mins where the Horizon Mirage Server is a VM on a standalone ESXi server with local disk with two 500GB 7.2RPM SATA disks extended into one datastore. Setup 2 The Horizon Mirage server was installed on a physical server with 500GB 7.2RPM SATA Disks on Raid 1.  This took 52mins. Separately, my colleague did a test as well in our office network which...