Fetch history with no_attributes
for entities that do not need them
#12082
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.
Proposed change
Dropping the attributes on the frontend in testing was much faster:
with - Run Time: real 1.891 user 0.041000 sys 0.053000
without - Run Time: real 0.074 user 0.034000 sys 0.040000
In testing all my entity history graphs on my production install load in < 1s now
This should be backwards compatible as the history api will ignore
no_attributes
if its not supported and we end up with the attributes in memory even if they aren't needed (as it currently functions).Type of change
Example configuration
Additional information
Checklist
If user exposed functionality or configuration variables are added/changed: