Raffaele Giordanelli About Memory Ballooning

One of the biggest tasks facing system administrators today is finding efficient host memory reclamation techniques to support memory overcommitment, says Raffaele Giordanelli, CEO and CTO of Eco4Cloud.

One way to do this is through ballooning.

"Virtual memory ballooning is a RAM memory reclamation technique used by a ESX hypervisor to allow the physical host system to retrieve unused memory from certain guest VMs and share it with others," he says.

Raffaele recently checked in with us to share more of his expert insight on managing memory and ballooning. Here’s what he had to say:

What are the most common frustrations for VMware administrators related to managing memory?

RAM memory is the bottleneck resource in a virtualized environment, mainly because of the use of overcommitment. I think the main frustration related to its management is the plenty of outright wrong requirements published by software vendors.

Wrong assignments force system administrators to assign too many resources – RAM memory above all – which leads to huge resources waste. In the case of CPU, it can also lead to performance decrease due to high latency (CPU ready time).

How can administrators manage memory more efficiently?

At Eco4Cloud we built an extensive software suite to automate several aspects of virtualized IT administration and increase performance. For example, with Eco4cloud Smart Ballooning, based on VMware memory reclamation techniques, unused memory of certain VMs can be released to ESXi and can redistributed. With VMware Ballooning, VMs are able to release memory when physical host reaches a hard memory usage threshold (typically 94 percent). On the other hand, with Smart Ballooning, you can reclaim memory continuously, recovering up to 15 percent of RAM memory from each VM.

What are the advantages of ballooning?

Memory ballooning allows the total amount of RAM required by guest VMs to exceed the amount of physical RAM available on the host in stressful situations. When the host system runs low on physical RAM resources, memory ballooning reclaims it from VMs no longer using it.

What are the potential disadvantages?

Ballooning can negatively affect the performance of the guest Operating System because it is a heavily CPU-intensive process, as it monitors all the RAM memory of a host consuming too much memory. It potentially affects system stability, as ballooning can remove large amounts of memory from the guest operating system. So its usage must be well thought.

How should VMware administrators be using ballooning?

System administrators need to know what kind of applications run in the virtual machines, and disable Memory Ballooning selectively on the virtual machines running applications that can potentially crash if the ESX host removes memory pages through ballooning.

What do you think are the most common misconceptions among administrators about ballooning?

Ballooning without supervision can negatively affect the performance of the guest, which in a production environment is a dangerous behavior.

Connect with Raffaele on LinkedIn.

Sign up for our newsletter.

Raffaele Giordanelli About Memory Ballooning

Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials


Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).


immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance


Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.


While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace


No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data


IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.


immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence


CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.


As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.