fix: visualization and dashboard scalability for large datasets#17
Open
fix: visualization and dashboard scalability for large datasets#17
Conversation
…bgl context exhaustion
…ith large datasets
This file contains hidden or 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
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.
Summary
Fixes critical performance and rendering issues when working with large numbers of visualizations (2000+).
rendered_outputandcodeblobs, returning aVisualizationSummaryinstead — response dropped from ~100MB to ~900KBpageandper_pagequery params withLIMIT/OFFSETto the visualizationslist endpoint (default 24 per page)
instead of rendering 2000+ animated cards simultaneously (which caused a 2+ minute browser freeze from stagger
animations)
IntersectionObserver— only visible panels mounttheir
VizRenderer, preventing browser WebGL context exhaustion (gl-shader: Error compiling shader: null) whendashboards have many 3D Plotly charts
instead of their actual rendered output on the detail page
Test plan
/visualizationswith 2000+ visualizations — page loads instantly with pagination controls/dashboards/:idwith many 3D Plotly panels — no WebGL shader errors, panels lazy-load on scroll