[enhancement] Optimize JSON decoding for sessions when applying filtering criteria #3343
Conversation
This file contains 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
vkarak
added
prio: normal
enhancement
reporting
vkarak
force-pushed
the
bugfix/optimize-json-decoding
branch
from
cf2a106 to
917a5ae
Compare
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.
When decoding and filtering sessions based on filtering criteria (
?syntax) we do not decode the whole session, but rather only the session informationsession_infosub-object. We then apply the filtering criteria and we only decode fully a session if it passes the filter. This way, the efficiency of queries based on the?filtering syntax is considerably improved as only the required subsets of sessions are fully decoded and not the whole DB.Closes #3340.