Optimize Arm applications and shared libraries with BOLT
Introduction
Overview
Instrument MySQL with BOLT
Run a new workload using BOLT and merge the results
Instrument shared libraries with BOLT
Review the performance results
Next Steps
Optimize Arm applications and shared libraries with BOLT
Who is this for?
This is an advanced topic for performance engineers and software developers targeting Arm platforms who want to optimize application binaries and shared libraries using BOLT.
What will you learn?
After completing this Learning Path, you'll be able to perform the following tasks:
- Instrument and optimize application binaries for individual workload features using BOLT
- Collect and merge separate BOLT profiles to improve code coverage
- Optimize shared libraries independently of application binaries
- Integrate optimized shared libraries into applications
- Evaluate and compare performance across baseline, isolated, and merged optimization scenarios
Prerequisites
Before starting, you'll need the following prerequisites:
- An Arm-based Linux system with BOLT and Linux Perf installed
Summary
This summary was 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.
You’ll use BOLT with Linux Perf profiles to optimize an Arm application and its shared libraries. First, you’ll instrument a MySQL server build to generate workload-specific profiles, create separate traces for read-heavy and write-heavy runs, and merge them to broaden code layout guidance. Then, you’ll rebuild OpenSSL to make
libssl.so and libcrypto.so suitable for BOLT, collect profiles, and apply optimizations independently from the main binary. Finally, you’ll compare results across baseline, isolated, and merged scenarios using a consistent Sysbench configuration to assess the impact of application and library-level optimizations on throughput and latency.