Performance optimisation of GetStreamsRequiringSnapshots. #398
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.
Optimisation of the GetStreamsRequiringSnapshots SQL as execution time in my use case (just several streams, but one with over a million events) has been growing linearly with the size of the single large stream to atm take in excess of 45 seconds. This proposal cuts the execution time back down to ~1 second.
Note that I've only got an MsSql installation against which I can test the proposed modification to CommonSqlStatements...