-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Use measureme in self profiler #59515
Conversation
Looks like a good start! Eventually I'd like to have query names instead of dep-node names here but I don't know how to exactly do that yet. Have you done performance tests on Windows? If the mmap-sink performance worse than the file-sink there, I think I'd like to get rid of the For now, I think we should just ignore the category data. Later we could encode it in the I think we can just publish |
Originally I passed
I've been working on getting rustc to build on my Windows box. It's been a long time since I used it and my msvc toolchain was completely out of date. I think that's resolved now and I'm just waiting for LLVM to build. I should have the performance data tonight.
Ok that's fine. I'll remove the other unused
I'd personally vote for publishing on crates.io |
Results of testing on Windows:
|
Great, thanks for getting those numbers. Let's use the |
It looks like a recent PR fixed this for us by making |
Oh, wonderful! I can make that change tonight. Do we have consensus on how to add the |
Let's go via |
Note that |
@michaelwoerister Do you like the approach in edff02e better? |
I do -- but it still has some runtime overhead for cloning the query key. Could you try to add an associated constant to |
Oh yeah, that's a better idea |
I left a few comments. Looks like this is almost ready to merge. |
Thanks for the feedback @michaelwoerister! I've made those changes, pushed, and marked this PR as ready for review. |
@bors r=michaelwoerister |
📌 Commit 56e434d has been approved by |
[WIP] Implement event filtering for self-profiler. This is a first sketch for event filtering in the self-profiler, something that we'll want in order to keep profiling overhead low in the common case. The PR contains the commits from #59515 and, for the moment, is meant for performance testing. r? @wesleywiser
Use measureme in self profiler r? @michaelwoerister ~Changes are still very rough.~ ~I'm not sure what the right way to add the `measureme` dependency is. Currently it's just added with a relative path which Works On My Machine ™️.~ I'm also not sure what to do with the category data.
☀️ Test successful - checks-travis, status-appveyor |
…, r=wesleywiser Implement event filtering for self-profiler. This is a first sketch for event filtering in the self-profiler, something that we'll want in order to keep profiling overhead low in the common case. The PR contains the commits from rust-lang#59515 and, for the moment, is meant for performance testing. r? @wesleywiser
…, r=wesleywiser Implement event filtering for self-profiler. This is a first sketch for event filtering in the self-profiler, something that we'll want in order to keep profiling overhead low in the common case. The PR contains the commits from rust-lang#59515 and, for the moment, is meant for performance testing. r? @wesleywiser
…, r=wesleywiser Implement event filtering for self-profiler. This is a first sketch for event filtering in the self-profiler, something that we'll want in order to keep profiling overhead low in the common case. The PR contains the commits from rust-lang#59515 and, for the moment, is meant for performance testing. r? @wesleywiser
…, r=wesleywiser Implement event filtering for self-profiler. This is a first sketch for event filtering in the self-profiler, something that we'll want in order to keep profiling overhead low in the common case. The PR contains the commits from rust-lang#59515 and, for the moment, is meant for performance testing. r? @wesleywiser
…, r=wesleywiser Implement event filtering for self-profiler. This is a first sketch for event filtering in the self-profiler, something that we'll want in order to keep profiling overhead low in the common case. The PR contains the commits from rust-lang#59515 and, for the moment, is meant for performance testing. r? @wesleywiser
…, r=wesleywiser Implement event filtering for self-profiler. This is a first sketch for event filtering in the self-profiler, something that we'll want in order to keep profiling overhead low in the common case. The PR contains the commits from rust-lang#59515 and, for the moment, is meant for performance testing. r? @wesleywiser
…, r=wesleywiser Implement event filtering for self-profiler. This is a first sketch for event filtering in the self-profiler, something that we'll want in order to keep profiling overhead low in the common case. The PR contains the commits from rust-lang#59515 and, for the moment, is meant for performance testing. r? @wesleywiser
…, r=wesleywiser Implement event filtering for self-profiler. This is a first sketch for event filtering in the self-profiler, something that we'll want in order to keep profiling overhead low in the common case. The PR contains the commits from rust-lang#59515 and, for the moment, is meant for performance testing. r? @wesleywiser
…, r=wesleywiser Implement event filtering for self-profiler. This is a first sketch for event filtering in the self-profiler, something that we'll want in order to keep profiling overhead low in the common case. The PR contains the commits from rust-lang#59515 and, for the moment, is meant for performance testing. r? @wesleywiser
r? @michaelwoerister
Changes are still very rough.I'm not sure what the right way to add themeasureme
dependency is. Currently it's just added with a relative path which Works On My Machine ™️.I'm also not sure what to do with the category data.