Parallelise the history JSON loads for faster initial load times. #14
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.
Currently the history load code waits for each file to be returned before requesting the next. This modification requests all files at the same time and keeps count of how many are returned. Once they're all back, end_load_history is called as normal. Any files which fail to load are ignored, rather than stopping the load at the point.
Also correct the "applying history" error message to match the counter against the total - previously it finished with "119/120" because the files are numbered from 0.
As a by-product, for my test server using http/2 this halved the load time against the same code using http/1.1 due to the protocol's improvements in parallel resource loads.