XRP Ledger Upgrade Cuts Validator Memory Use
Two Ripple-operated validators recorded lower process memory after moving from xrpld 3.2.0 to 3.3.0, with heap trimming enabled.
Updated on Nov. 8, 2026 in Semiconductors
On August 6, 2026, xrpld 3.3.0 was released, enabling heap trimming for glibc builds. Two Ripple-operated validators on the XRP Ledger recorded lower average resident memory after the upgrade.
Why it matters
Lower memory use on validators can ease the hardware demands of running nodes on the XRP Ledger network. The results come from a limited set of Ripple-operated validators and a separate lab test, so their broader applicability is not established.
Average resident memory on the two validators fell by 2.7 GiB and 4.4 GiB after the upgrade, measured over 44-day and 38-day windows. The lab comparison found 14.8% lower memory on validator nodes and 18.2% on client-handler nodes, but it is unclear whether these gains apply beyond glibc builds.
The players
Ripple
Ripple is a San Francisco-based blockchain payments company that operates validators on the XRP Ledger.
XRP Ledger
The XRP Ledger is a public, decentralized blockchain network secured by independently run validator nodes.
The details
xrpld calls glibc's malloc_trim after a cache sweep, asking the allocator to return unused heap memory to the kernel. From version 3.3.0 onward, heap trimming is enabled for glibc builds, while builds using other allocators do not receive this change. Each measurement window began with a fresh process start.
Timeline
June 16, 2026: xrpld 3.2.0 measurement window begins.
July 31, 2026: xrpld 3.2.0 measurement window ends after 44 days.
August 6, 2026: xrpld 3.3.0 is released.
August 7, 2026: xrpld 3.3.0 measurement window begins, running 38 days.
The Tech Race
The change relies on glibc's malloc_trim, which returns unused heap memory to the operating system after cache sweeps. Its effect is limited to glibc builds, so it does not change memory behavior for software compiled with other allocators.
Operators running xrpld validators on glibc builds may see lower memory use after upgrading to 3.3.0, based on the measured windows. Those using other allocators will not receive the heap-trimming change.
The takeaway
Validator operators should consider the allocator they use before expecting the memory reduction from xrpld 3.3.0. Monitoring resident memory after an upgrade can confirm whether the change applies to a given setup.
Further reading
For related coverage of hardware-level memory and performance topics, see Semiconductors.
Source note: This article includes information reported by TokenPost.
