Fix table performance #5380
Closed
Fix table performance #5380
Conversation
This file contains 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
This performance issue is caused by table's data manipulating. Table replicates source data and always applies a new key to render data, which causing re-render when table's source data changed. Use index as key instead to prevent futher re-render, for now. Closes #4099
|
Thanks @YunSun-CN , iView table's performance is so hurt! but, I'think it will be much better if you expose a prop like 'keyColumnName' |
|
|
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.
This performance issue is caused by table's data manipulating.
Table replicates source data and always applies a new key to render
data, which causing re-render when table's source data changed.
Use index as key instead to prevent futher re-render, for now.
Closes #4099