Remove will_cache_on_disk_for_key_fn#154591
Remove will_cache_on_disk_for_key_fn#154591zetanumbers wants to merge 6 commits intorust-lang:mainfrom
will_cache_on_disk_for_key_fn#154591Conversation
This is the only remaining query with a non-trivial `cache_on_disk_if` condition, but previous perf experiments indicate that it can be removed entirely, with little or no measurable effect.
Queries with both `cache_on_disk` and `separate_provide_extern` will only disk-cache values for local keys. Other queries with `cache_on_disk` will disk-cache all values unconditionally.
|
@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.
…<try> Remove `will_cache_on_disk_for_key_fn`
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (0f75a34): comparison URL. Overall result: ❌✅ regressions and improvements - please read the text belowBenchmarking this pull request means it may be perf-sensitive – we'll automatically label it not fit for rolling up. You can override this, but we strongly advise not to, due to possible changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please do so in sufficient 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 4.0%, secondary 2.2%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 2.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 483.836s -> 484.325s (0.10%) |
Refactors
QueryVtablesand removeswill_cache_on_disk_for_key_fnas unnecessary indirection.Based and blocked on #154576.
Expecting perf improvements.