This is a bunch of random user feedback from my first try of austin + austin-tui.

Some user feedback about austin-tui HOT 4 OPEN

jonashaag commented on May 23, 2024

Some user feedback

from austin-tui.

Comments (4)

P403n1x87 commented on May 23, 2024 2

Update pausing and threshold are now available

from austin-tui.

jonashaag commented on May 23, 2024 1

The help prompt hints that the number should be in microseconds (us).

Ah! Only the austin one. austin-tui:

  -i INTERVAL, --interval INTERVAL
                        Sampling interval (default is 100 μs).

from austin-tui.

P403n1x87 commented on May 23, 2024

Hi. Thanks for stopping by to give feedback! Much appreciated

Regarding your points

The austin compile instructions miss a cd austin.

I will add that

Tmux breaks colors (see screenshot)

I haven't thought of testing the TUI over tmux so I wasn't aware of the issue. Some users suggest using tmux -2 to force tmux to use 256 colour support.

Ctrl + C does not work

What OS are you using? Ctrl + C seems to work fine on Linux (also on tmux).

It works great! :-) I love that you can switch threads so easily. It just works.

🎉 😄

The top-like view changes so quickly it's almost impossible to see the profile.

I was already considering adding a Pause command to freeze the screen.

-h doesn't say what unit the -i option should be given in.

The help prompt hints that the number should be in microseconds (us).

-i, --interval=n_us        Sampling interval (default is 500us).

perhaps I'll have to make this more explicit.

If you switch to full mode, it is annoying to scroll through hundreds of lines with 0.01% usage. Maybe a display threshold could help, or a way to collapse subtrees?

Good idea. I was already thinking about adding the possibility of collapsing/expanding nodes.

I don't know what the CPU and mem graphs on the upper right mean. Consumption relative to total system resources? Consumption relative to parent Python process?

CPU gives pretty much the same number that you would see from top for the parent process, hence total CPU usage by the parent process. The memory plot is autoscaled and shows you how memory fluctuates during execution (for all the sampled processes).

from austin-tui.

jonashaag commented on May 23, 2024