Can someone run perf for https://github.com/rust-lang/rust/pull/72776 again?
Can someone run perf for https://github.com/rust-lang/rust/pull/72822? (done, thanks :heart: )
Can someone run perf for https://github.com/rust-lang/rust/pull/72962? Have to sleep now.
Seems like I made a mistake with using
Lrc... should now be fixed and can be restarted x.x
Can someone rerun perf for https://github.com/rust-lang/rust/pull/72962?
I now cache
ObligationCause::dummy. I previously had a few million copies of it on the heap... I have to admit I don't
know if this number of allocations is actually relevant :sweat_smile:
Where is the :heap: emoji?
:trash_can: (that's the closest I could think of)
I can't access thhat commit :oh_no: apparently My PR is still in the perf queue?
Queue (10 total):
Times are local.
Commit Date SHA Reason
try commit 8ff82fab989f4 TryCommit
6/4/2020, 4:16:13 PM 3d5d0f898c2f3 TryParent
try commit ba0ecc9e775e6 TryCommit // <- my PR
Ok... I removed another few hundred thousand small allocations. Not sure if we want to perf it again or just merge it with
Feel free to either review or start another perf run :sparkles:
Can someone perf https://github.com/rust-lang/rust/pull/71154? Let's see how far my current approach can get...
^ it seems like that PR didn't actually get added to the perf queue :thinking:
Can someone perf https://github.com/rust-lang/rust/pull/71154 again, I think this new approach might be better... :oh_no:
Did this try build get cancelled due to a merge conflict? Or is this message sent once the PR is added to the queue? https://github.com/rust-lang/rust/pull/71154#issuecomment-641267489
Given that it’s not in the homu queue anymore, I’d guess it got cancelled
Well, let's try https://github.com/rust-lang/rust/pull/71154 again, please perf :sweat_smile: