top of page

Taming Memory Pressure with LMDB

  • Writer: Maryanne Normann
    Maryanne Normann
  • Aug 20
  • 1 min read
Pinterest
Pinterest

Pinterest’s NGAPI switched to LMDB to ease memory pressure from its gevent-based multi-process setup. The change cut memory use by 4.5% (~4.5 GB per host), letting them raise processes per host from 64→66, handle more requests with better CPU utilization, and ultimately reduce fleet size—improving efficiency and reliability for Pinners.


For the full story, click here.



Recent Posts

See All
The Achilles Heel of LRU Caches

Ever since we released LMDB, our advice to software designers has been "don't do application level caching. Let the kernel handle it for...

 
 
About the LDAP Load Gen Project

LDAP Load Generator is a tool we use at Symas to drive load tests for OpenLDAP releases. What Can It Do? Add, Modify, Delete, Read,...

 
 
bottom of page