Stream: t-compiler/wg-self-profile

Topic: profiling per source code location


nikomatsakis (Mar 09 2019 at 11:04, on Zulip):

BTW, one thing we had talked about was adding the ability to organize the profile per DefId or source-code location as well, so that people could get an idea what part of their programs are forcing compilation to take a long time. This just came up when I was talking to @Frank McSherry, so it popped in my mind again -- I know it's not on the MVP plans, but do we still have this down as a kind of "eventually" sort of item?

nikomatsakis (Mar 09 2019 at 11:04, on Zulip):

@Frank McSherry may have some good ideas of what specifically they want, as well. I remember @Alex Crichton also being interested.

Wesley Wiser (Mar 09 2019 at 16:31, on Zulip):

@Alex Crichton and @David Tolnay asked me about this at All Hands. We should have some kind of place to track these longer term ideas. Right now we're blocked on standardizing the export format from rustc. After that happens, a lot of these tools could probably be developed rather independently. Which might be a good opportunity for new people wanting to contribute.

mw (Mar 11 2019 at 09:37, on Zulip):

profiling per query key is definitely planned. Source-code locations I don't know...

nikomatsakis (Mar 13 2019 at 18:20, on Zulip):

I think per-key is roughly the same thing as source-code locations

Last update: Nov 17 2019 at 08:15UTC