A profiler is often the tool of choice to identify performance bottlenecks. Profiling is suitable to identify where performance is lost in a given piece of software. The profiler outputs a profile, a statistical summary of observed events, which you may use to discover which functions took the most time to execute. However, a profiler won’t report why some identified functions are the bottleneck. Bottlenecks might only occur when specific conditions are met, conditions that are sometimes impossible to capture by a statistical profiler, or impossible to reproduce with an application altered by the overhead of an event-based profiler.

• Profilerpedia Software Profiling Tool Catalog
  • mhansen/profilerpedia Catalog of profilers, profile data formats, data format converters, and profile analysis UIs.
  • Profile Data Formats
    • uftrace
• Perfetto System profiling, app tracing and trace analysis
  • google/perfetto) Performance instrumentation and tracing for Android, Linux and Chrome (read-only mirror of https://android.googlesource.com/platform/external/perfetto/

Wikipedia

• Profiling (computer programming) is a form of dynamic program analysis that measures, for example, the space (memory) or time complexity of a program, the usage of particular instructions, or the frequency and duration of function calls.
  • Профилирование (информатика) сбор характеристик работы программы, таких как время выполнения отдельных фрагментов (обычно подпрограмм), число верно предсказанных условных переходов, число кэш-промахов и т. д.