Optimize Table rendering for large data sets#629
Merged
Conversation
novykh
approved these changes
Jul 13, 2026
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
Why
The current Table path creates work proportional to the complete row population. At roughly 5,000 nodes this makes scrolling and unrelated UI operations visibly freeze. This shared seam allows application consumers to remain fluent at 50,000 logical rows without changing payloads or user-visible results.
Measured hot-path exception
The opt-in directCellContent path deliberately uses one tokenized styled row with native repeated cell sections, while resolving colors and sizing from netdata-ui theme tokens.
A controlled production-bundle A/B test used the same 1,393-alert table and the same 1,100 px scroll:
The ordinary Table path remains unchanged and continues to use the existing netdata-ui components. The exception is opt-in and exists only where the styled-component cost is measurable in the scroll hot path.
Validation
Release order
Companion: netdata/cloud-frontend#5609.
This PR must merge and publish before the companion cloud-frontend PR. The frontend dependency and lockfile will then be updated to the exact released version before that PR is merged.
Global table-header tooltip milestone
Additional validation
Release gate
Versions 5.4.17 and 5.4.18 are already published. This PR must receive the next version through the normal release process and be published before the companion frontend dependency and lockfile are updated.