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
Review frequently asked questions
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.
BOLT produces a profile file in
.fdata format, such as profile-writeonly.fdata. These files are later used to optimize the binary and can be merged to improve coverage.Either approach works. The steps allow reusing the previously instrumented binary or generating a new instrumented variant as long as you produce a new
.fdata profile for each workload.The path optimizes
libssl.so and libcrypto.so. If system libraries are stripped, rebuild OpenSSL from source with relocations enabled so BOLT can instrument and optimize them.The shared libraries are optimized independently of the application binary. The path focuses on rebuilding OpenSSL for symbol information and then integrating the optimized libraries with the application.
Sysbench is run with
--time=0 --events=10000 to complete exactly 10,000 requests per thread. Use this consistent configuration to compare baseline, application-only, and merged-with-library optimization scenarios.