Saved in:
| Main Author: | |
|---|---|
| Format: | Recurso digital |
| Language: | |
| Published: |
Zenodo
2026
|
| Online Access: | https://doi.org/10.5281/zenodo.19163536 |
| Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
Table of Contents:
- <p>One of the major challenges of modern distributed systems is to understand CPU consumption patterns. Existing profiling tools cannot indicate which experiments or traffic patterns caused the CPU to be busy. This creates challenges for developers in diagnosing performance issues. The proposed system uses unique sequence tagging to correlate profiling with attribution. Each profile is tagged with the id of the associated request, which is persisted through the profile's execution, and is joined at the batch analytics stage with the request metadata, including the experiment identifiers, the latency classifications and the traffic slice identification. Developers can query the dataset for profiles matching their attribution settings, then visualize the result in a flame graph. The flame graph is a method of visualizing profiles in an easy to understand manner, displaying what paths through code are consuming too much CPU in the context of an experiment. By enabling attribution-based profiling, moved performance debugging efforts from relying on infrastructure engineers and experts to be self-serve by product developers. As a result, performance regressions can be detected earlier in the development cycle and their occurrence prevented, saving computational resources and protecting system stability in production environments serving global traffic. The same attribution can be applied on other dimensions, such as memory or network profiling</p>