Skip to main content

TPS (Transparent Page Sharing) and UNMAP

TPS (Transparent Page Sharing) and UNMAP are distinct VMware vSphere features that address different aspects of resource management. TPS focuses on memory optimization by deduplicating identical memory pages across virtual machines, while UNMAP, a SCSI command, enables thin-provisioned storage arrays to reclaim unused space by identifying and discarding deleted blocks. 

TPS (Transparent Page Sharing): 

Function:

TPS identifies and consolidates identical memory pages used by multiple VMs, reducing overall memory consumption. 

Mechanism:

It works by comparing the content of memory pages and storing only one copy if they are identical, effectively deduplicating memory. 

Intra-VM vs. Inter-VM:

TPS can operate within a single VM (intra-VM) or across multiple VMs (inter-VM). 

Security Considerations:

While TPS can enhance memory efficiency, it also presents a potential security risk as it can be exploited to access data on other VMs. VMware has addressed this by introducing changes to TPS behavior, including restricting inter-VM TPS by default. 

UNMAP: 

Function: UNMAP is used to reclaim unused space on thin-provisioned storage arrays. It informs the storage array that certain blocks are no longer in use and can be returned to the free pool. 

Mechanism: UNMAP is a SCSI command sent by the hypervisor to the storage array, indicating which blocks are no longer needed. 

Benefits: UNMAP allows for better utilization of storage capacity by allowing the array to reuse freed blocks. 

VMFS-6: UNMAP is automatically enabled for VMFS-6 datastores. 

Monitoring: You can monitor UNMAP operations using tools like esxtop. 






Comments

Post a Comment

Popular posts from this blog

Quick Guide to VCF Automation for VCD Administrators

  Quick Guide to VCF Automation for VCD Administrators VMware Cloud Foundation 9 (VCF 9) has been  released  and with it comes brand new Cloud Management Platform –  VCF Automation (VCFA)  which supercedes both Aria Automation and VMware Cloud Director (VCD). This blog post is intended for those people that know VCD quite well and want to understand how is VCFA similar or different to help them quickly orient in the new direction. It should be emphasized that VCFA is a new solution and not just rebranding of an old one. However it reuses a lot of components from its predecessors. The provider part of VCFA called Tenenat Manager is based on VCD code and the UI and APIs will be familiar to VCD admins, while the tenant part inherist a lot from Aria Automation and especially for VCD end-users will look brand new. Deployment and Architecture VCFA is generaly deployed from VCF Operations Fleet Management (former Aria Suite LCM embeded in VCF Ops. Fleet Management...
Post a Comment
Read more
  Issue with Aria Automation Custom form Multi Value Picker and Data Grid https://knowledge.broadcom.com/external/article?articleNumber=345960 Products VMware Aria Suite Issue/Introduction Symptoms: Getting  error " Expected Type String but was Object ", w hen trying to use Complex Types in MultiValue Picker on the Aria for Automation Custom Form. Environment VMware vRealize Automation 8.x Cause This issue has been identified where the problem appears when a single column Multi Value Picker or Data Grid is used. Resolution This is a known issue. There is a workaround.  Workaround: As a workaround, try adding one empty column in the Multivalue picker without filling the options. So we can add one more column without filling the value which will be hidden(there is a button in the designer page that will hide the column). This way the end user will receive the same view.  
Post a Comment
Read more

Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware

 ðŸ”¹ Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works  1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS.  2. ESXi detects low free memory on the host.  3. ESXi inflates the balloon in selected VMs.  4. Balloon driver occupies guest memory, making the OS think RAM is full.  5. Guest OS frees idle / unused pages (because it believes memory is needed).  6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens?  • Host free memory is very low.  • ESXi wants the VM to release unused pages before resorting to swapping. Example  • Host memory: 64 GB  • VMs used: 62 GB  • Free: 2 GB → ESXi triggers ballooning  • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...
Post a Comment
Read more