search_graph: strengthen provisional cache by tracking more info in the happy path#155917
search_graph: strengthen provisional cache by tracking more info in the happy path#155917lcnr wants to merge 2 commits intorust-lang:mainfrom
Conversation
|
|
| { | ||
| continue; | ||
| } | ||
| } |
There was a problem hiding this comment.
this fast path meant exponential blowup in ml-kem ended up causing a hang. let's instead just track all nested goals
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Memories of a forgotten past
This comment has been minimized.
This comment has been minimized.
bf814f9 to
31ca4ac
Compare
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (4fcc7a6): comparison URL. Overall result: ❌ regressions - please read:Benchmarking means the PR may be perf-sensitive. It's automatically marked not fit for rolling up. Overriding is possible but disadvised: it risks changing compiler perf. Next, please: If you can, justify the regressions found in this try perf run in writing along with @bors rollup=never Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 0.7%, secondary 7.9%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 2.0%, secondary 0.6%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 489.39s -> 485.808s (-0.73%) |
See the added inline comment
r? BoxyUwU