klp VS viztracer

Angle-grinder is really nice and the successor of sumoshell (by the same author).

I maintain a list of tools like these as part of the docs for my own tool klp (https://github.com/dloss/klp), which I think has a few useful features that are not in angle-grinder, but is orders of magnitude slower, because it's implemented in pure Python instead of Rust.

Hello HN community,

I’m currently developing a log parsing and log viewing tool (https://github.com/dloss/klp) and am in need of realistic log file examples that I can include in my documentation and use for internal testing. Specifically, I’m looking for log files that are:

1. Publicly available and permissible for redistribution under an Open Source license (ideally MIT license).

2. Structured logs, either in JSONL (JSON Lines) or logfmt format.

The purpose is to show how my tool can be used to effectively handle real-world data, and to identify new features that would be useful.

If anyone knows of datasets, repositories, or sources where I could find such log files, your guidance would be immensely helpful.

Thank you in advance for your assistance and suggestions!

* https://github.com/gaogaotiantian/viztracer get a timeline of execution vs call-stack (great to discover what's happening deep inside pandas)

Do not use bad instrumenting profilers. A good modern tracing-based instrumenting profiler provides so much more actionable information and insights into where problems are than a sampling profiler it is ridiculous.

As a example consider viztracer [1] for Python. By using a aggregate visualizer such as a flame graph you can figure out what is taking the most time then you can use a tracing visualizer to figure out the exact call stacks and system execution and state that caused it. Not only that, a tracing visualizer lets you diagnose whole system performance and makes it trivial to identify 1 in 1000 anomalous execution patterns (with a 4k screen a anomalous execution pattern stands out like a 4 pixel dead spot). In addition you also get vastly less biased information for parallel execution and get easy insights into parallel execution slowdowns, interference, contention, and blocking behaviors.

The only advantages highlighted in your video that still apply to a good instrumenting profiler are:

1. Multi-language support.

2. Performance counters (though that is solved by doing manual tracking after you know the hotspots and causes).

3. Overhead (if you are using low sampling frequency). Even then a good tracing instrumentation implementation should only incur low double-digit percent overhead and maybe 100% overhead in truly pathological cases involving only small functions where the majority of the execution time is literally spent in function call overhead.

4. No need for recompilation, but you are already looking to make performance changes and test so you already intend to rebuild frequently to test those experiments. In addition, the relative difference in information is so humongous that this is not even worth contemplating unless it is a hard requirement like evaluating something in the field.

[1] https://github.com/gaogaotiantian/viztracer

Actually it has explicit support for async task based reporting:

https://github.com/gaogaotiantian/viztracer#async-support

Let us run perf on this, similarly to what we did to example0.py. However, we add the argument -k CLOCK_MONOTONIC so that we use the same clock as VizTracer and ask VizTracer to generate a JSON, instead of an HTML file: