Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

cache upgraded reports #2970

Closed
rade opened this issue Dec 8, 2017 · 0 comments
Closed

cache upgraded reports #2970

rade opened this issue Dec 8, 2017 · 0 comments
Assignees
@rbruggem
Labels
chore Related to fix/refinement/improvement of end user or new/existing developer functionality performance Excessive resource usage and latency; usually a bug or chore

Comments

@rade
Copy link
Member

rade commented Dec 8, 2017

ATM we upgrade reports after merging. That means as successive queries will re-upgrade many of the same reports.

Instead we should upgrade the reports we fetch, and store these in the in-process cache instead of the raw reports.
@rade rade added chore Related to fix/refinement/improvement of end user or new/existing developer functionality performance Excessive resource usage and latency; usually a bug or chore labels Dec 8, 2017
@rbruggem rbruggem self-assigned this Dec 12, 2017
@rbruggem rbruggem mentioned this issue Dec 12, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rbruggem rbruggem

Labels
chore Related to fix/refinement/improvement of end user or new/existing developer functionality performance Excessive resource usage and latency; usually a bug or chore
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rade @rbruggem