Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.NET Profiling for ASP.NET Core #2316

Open
4 tasks
bruno-garcia opened this issue Apr 19, 2023 · 2 comments
Open
4 tasks

.NET Profiling for ASP.NET Core #2316

bruno-garcia opened this issue Apr 19, 2023 · 2 comments

Comments

@bruno-garcia
Copy link
Member

bruno-garcia commented Apr 19, 2023

Follow up from:

  • collect Microsoft-Windows-DotNETRuntime rundown provider (loaded libs, etc) in a separate session and merge with actual samples later during processing, if possible (merging nettrace files, or having a custom provider for TraceLog).
  • Or maybe we don't even need to collect these because we're in the same process? can we hack our way around and get the libraries from the current process instead? Probably not so easy because it also somehow stack walking if I'm not mistaken.
  • We'll use GlobalMode to set the behavior: all threads in process (global Mode) or only activity/request (server mode)
  • Consider capturing only the current "activity", i.e. not all threads but only what belongs to the transaction.
@ericsampson
Copy link

Very exciting. How long do you think it'll be before external users are able to give it a go, assuming that we acknowledge that it's "alpha/beta caveat emptor" :)

@mattjohnsonpint
Copy link
Contributor

First we need to get through #2315, which is blocked by microsoft/perfview#1829

Then we can better estimate this one. It will likely be a while.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Archived in project
Development

No branches or pull requests

4 participants