RAR does not write to cache file on rebuilds#2692
Merged
cdmihai merged 3 commits intodotnet:vs15.5from Nov 6, 2017
Merged
Conversation
From af21963
Using TryAdd means that the first value that gets into the cache does not ever get overwritten, even when the data is stale.
Contributor
Author
Member
|
I likely regressed this. |
Contributor
Author
|
Nothing interesting here. Build time suggests positive improvement, as every case seems to be an improvement, with largest in the mvc project which is RAR heavy. Evaluation: Time (ms)
Evaluation: Memory (bytes)
Build: Time (ms)
Build: Memory (bytes)
|
AndyGerlicher
approved these changes
Nov 6, 2017
Contributor
AndyGerlicher
left a comment
There was a problem hiding this comment.
Approved, @cdmihai merge it please.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #2687
Cause of the issue:
Fix: I chose to reuse the old code, wrap it with a guarding collection (to ensure an entry is checked for staleness only once), and ported over the change to replace stale entries from the process wide cache. Did this because the old code had an extra optimization: if the process wide cache had a more recent entry than the project specific cache, it would update the project specific cache from the process cache.
Before / After memory
Before / After CPU
