Don't reload unit data if nothing changed on disk when reading Campaigns #2286
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.
I noticed this while debugging this weekend, but basically we were reloading mech data even if nothing changed on disk during CPNX load. Now, this nearly always hits the hot cache and does not make a big impact for most users. However, when I moved MHQ over to a spinning disk on my machine, this shaved about 10 seconds off CPNX load times. Folks should not expect that amount of speedup in general, as most users do not have a few hundred customs (from all of the CPNXs shared on bug reports).