austin

Python frame stack sampler for CPython (by P403n1x87)

Austin Alternatives

Similar projects and alternatives to austin

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

austin reviews and mentions

Posts with mentions or reviews of austin. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-02-10.
  • Memray – A Memory Profiler for Python
    10 projects | news.ycombinator.com | 10 Feb 2024
    I collected a list of profilers (also memory profilers, also specifically for Python) here: https://github.com/albertz/wiki/blob/master/profiling.md

    Currently I actually need a Python memory profiler, because I want to figure out whether there is some memory leak in my application (PyTorch based training script), and where exactly (in this case, it's not a problem of GPU memory, but CPU memory).

    I tried Scalene (https://github.com/plasma-umass/scalene), which seems to be powerful, but somehow the output it gives me is not useful at all? It doesn't really give me a flamegraph, or a list of the top lines with memory allocations, but instead it gives me a listing of all source code lines, and prints some (very sparse) information on each line. So I need to search through that listing now by hand to find the spots? Maybe I just don't know how to use it properly.

    I tried Memray, but first ran into an issue (https://github.com/bloomberg/memray/issues/212), but after using some workaround, it worked now. I get a flamegraph out, but it doesn't really seem accurate? After a while, there don't seem to be any new memory allocations at all anymore, and I don't quite trust that this is correct.

    There is also Austin (https://github.com/P403n1x87/austin), which I also wanted to try (have not yet).

    Somehow this experience so far was very disappointing.

    (Side node, I debugged some very strange memory allocation behavior of Python before, where all local variables were kept around after an exception, even though I made sure there is no reference anymore to the exception object, to the traceback, etc, and I even called frame.clear() for all frames to really clear it. It turns out, frame.f_locals will create another copy of all the local variables, and the exception object and all the locals in the other frame still stay alive until you access frame.f_locals again. At that point, it will sync the f_locals again with the real (fast) locals, and then it can finally free everything. It was quite annoying to find the source of this problem and to find workarounds for it. https://github.com/python/cpython/issues/113939)

  • Pystack: Like Pstack but for Python
    3 projects | news.ycombinator.com | 7 Jun 2023
  • High performance profiling for Python 3.11
    2 projects | /r/Python | 31 Oct 2022
  • What are my Python processes at?
    1 project | news.ycombinator.com | 1 Feb 2022
  • tqdm (Python)
    24 projects | news.ycombinator.com | 16 Dec 2021
    Just wanted to add Austin: Python frame stack sampler for CPython written in pure C (https://github.com/P403n1x87/austin)
  • Pyheatmagic: Profile and view your Python code as a heat map
    7 projects | news.ycombinator.com | 2 Nov 2021
  • Spy on Python down to the Linux kernel level
    2 projects | news.ycombinator.com | 28 Sep 2021
    If you follow the call stack carefully you should be able to get to the point where sklearn calls ddot_kernel_8 (indirectly in this case). Austin(p) reports source files as well, so that shouldn't be a problem (provided all the debug symbols are available). If you're collecting data with austinp, don't forget to resolve symbol names with the resolve.py utility (https://github.com/P403n1x87/austin/blob/devel/utils/resolve..., see the README for more details: https://github.com/P403n1x87/austin/blob/devel/utils/resolve...)
  • (How to) profile python code?
    4 projects | /r/learnpython | 21 Aug 2021
  • Spy on the Python garbage collector with Austin 3.1
    1 project | news.ycombinator.com | 19 Aug 2021
  • Austin 3: 0-instrumentation, 0-impact Python CPU/wall time and memory profiling
    1 project | news.ycombinator.com | 5 Jul 2021
  • A note from our sponsor - WorkOS
    workos.com | 24 Apr 2024
    The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more β†’

Stats

Basic austin repo stats
12
1,353
7.5
15 days ago

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com