-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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.
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
[Feature Request] Performance improvement for large Table's #4359
Comments
mark. |
I'm also looking forward this. Instead of pagination, I should be able to use some other tool, like vue-infinite-scroll or clusterize.js. |
Just a sidenote, using clusterize.js directly might not be possible, because clusterize.js is GPLv3. |
I'm suffering a lot of performance issues due to a large table with constant updates requirement (real time data). It's killing my CPU with more than 50+ rows, even with pagination/inifnite scrolling. Any tips? |
None so far, I investigated this issue a lot, and conclusion is, without substantial changes to the table implementation in ElementUI itself, there is nothing you can do. I ended up using Handsontable - fit's our data size well enough. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Pretty much actual still. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Why, hello there, stale bot. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Stale bot, old friend! How have you been? |
Existing Component
Yes
Component Name
Table
Description
Right now there seems to be no performance optimizations for large data tables, think, 100s of thousands of rows. Perhaps something like https://clusterize.js.org could be implemented here, as because otherwise the component has a quite significant performance degradation, even sooner than raw html tables.
The text was updated successfully, but these errors were encountered: