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

Report optimizations (generalized) #570

Open
sei-bstein opened this issue Dec 16, 2024 · 0 comments
Open

Report optimizations (generalized) #570

sei-bstein opened this issue Dec 16, 2024 · 0 comments
Assignees
@sei-bstein
Labels
bug: non-breaking Issues that aren't desirable but don't directly impact app behavior.

Comments

@sei-bstein
Copy link
Contributor

Some of the bigger reports (challenges, enrollment, players) can be both slow and memory-hungry, especially on initial loads when they're unconstrained.

Paths of investigation

  • Not issuing the report request immediately upon arrival with no filters
  • More efficient query construction
  • Strategies to avoid loading the entire dataset into memory
@sei-bstein sei-bstein added the bug: non-breaking Issues that aren't desirable but don't directly impact app behavior. label Dec 16, 2024
@sei-bstein sei-bstein self-assigned this Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sei-bstein sei-bstein

Labels
bug: non-breaking Issues that aren't desirable but don't directly impact app behavior.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sei-bstein