Improve workload performance with glibc and Large System Extensions
Introduction
Build Glibc with LSE
Start MongoDB utilizing the newly built Glibc with LSE
Benchmark MongoDB with YCSB
Compare the results with LSE and NoLSE
Next Steps

  Log an issue

  Fork and edit

  Discuss on Discord

Explore related resources

Find more information about the topics in this Learning Path:

Give feedback

How would you rate this Learning Path?

Review frequently asked questions

AI-assisted

These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
How do I start MongoDB with the custom glibc?
First, copy libcrypt.so into the custom glibc build’s crypt directory. Then, launch mongod through testrun.sh with mongodb.conf and the WiredTiger cache setting.
Which MongoDB version should I build for the benchmark?
Use the repository tag r5.3.2.
Which YCSB workload should I run for the comparison?
Use a single YCSB workload profile and keep it identical across both LSE and NoLSE runs to compare results under consistent conditions.
What output should I capture from the NoLSE baseline to compare later?
Record the summary lines that include [OVERALL] RunTime(ms) and [OVERALL] Throughput(ops/sec). The example output also shows GC statistics that you can keep for reference.
What performance uplift does the example report for LSE?
The example reports about 3.14% uplift: throughput increases from 6,662.13 operations per second with No-LSE glibc to 6,871.61 operations per second with LSE glibc.

Share

Tell others about this Learning Path.

Back
Return to Servers and Cloud Computing