-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Profiling specific threads? #39743
Comments
Looking at Lines 677 to 724 in 0d47bfe
|
Do we? I don't see it in there. :) did you mean to type "we currently don't record"? But I see that we could record it! Thanks for linking me to the right spot to look ❤️ |
@vchuravy - per your suggestion, i gave this a shot here: It seems like it should be pretty straightforward, actually, but the code I wrote doesn't seem to affect anything. Even the Line 675 in 57cab58
|
Yes...
Ah yes if you are on that other operating system, that only pretends to be unix. Lines 494 to 542 in 0d47bfe
|
Haha 🙈 it didn't seem like a likely typo, but i read the code over a few times to be sure 😋 Cool, thanks again for the second link! 😁 |
What does "mach" refer to? I see it all the time, but i have never actually asked. |
Closed by #41742. |
Are there any plans for configuring the
Profile
profiler to only collect profiles for a specific threadid?It would be nice to e.g. only profile what's happening on threadid 1.
The use case I have in mind is that we're starting an
HTTP.jl
HTTP Server on thread 1, viaHTTP.serve(server=tcp) do http_request ; ... end
, which from what I understand uses@async
to schedule the provided callback on new Tasks, on the current thread. I am interested in profiling the performance and utilization of just that one thread.Is this something that could be easily supported and added to
Profile
? Or maybe something that could be performed in post-processing of the collected profile data? Do we record a thread id in the traces we collect? (I think we don't, but maybe i'm missing something?)Thanks! 🙂 ❤️ 📈
The text was updated successfully, but these errors were encountered: