viztracer

VizTracer is a low-overhead logging/debugging/profiling tool that can trace and visualize your python code execution. (by gaogaotiantian)

Viztracer Alternatives

Similar projects and alternatives to viztracer

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better viztracer alternative or higher similarity.

viztracer reviews and mentions

Posts with mentions or reviews of viztracer. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-04-10.
  • Ask HN: C/C++ developer wanting to learn efficient Python
    4 projects | news.ycombinator.com | 10 Apr 2024
    * https://github.com/gaogaotiantian/viztracer get a timeline of execution vs call-stack (great to discover what's happening deep inside pandas)
  • GCC Profiler Internals
    1 project | news.ycombinator.com | 21 May 2022
    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

  • Memray is a memory profiler for Python by Bloomberg
    8 projects | news.ycombinator.com | 20 Apr 2022
    Actually it has explicit support for async task based reporting:

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

  • Tracing and visualizing the Python GIL with perf and VizTracer
    10 projects | dev.to | 14 Jan 2021
    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:
  • A note from our sponsor - SaaSHub
    www.saashub.com | 18 Apr 2024
    SaaSHub helps you find the best software and product alternatives Learn more →

Stats

Basic viztracer repo stats
5
4,304
7.7
12 days ago
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com