Is there a preferred way of profiling `pants`? It ...
# plugins
b
Is there a preferred way of profiling
pants
? It being a Python app, I could try to see if I could use
py-spy
, but wanted to ping y'all first
That also wouldn't profile the native Rust code AFAIK
h
py-spy
is great! That's what Stu recommends and I used it last week
w
“it depends”
i use

macOS instruments

for most things… i think that the Linux equivalent would be a gui of some sort for
perf
h
FYI this page also: https://www.pantsbuild.org/v2.8/docs/contributions-debugging, just updated with some quick fixes per the docs audit
w
the thing that we don’t have, but which would likely be very, very useful, would be rendering aggregated workunits by type.
1