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.

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

Open
Addvilz opened this issue Apr 20, 2017 · 11 comments
Open

[Feature Request] Performance improvement for large Table's #4359

Addvilz opened this issue Apr 20, 2017 · 11 comments

Comments

@Addvilz
Copy link

Addvilz commented Apr 20, 2017

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.

@xmflswood
Copy link

mark.

@fergardi
Copy link

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.

@Addvilz
Copy link
Author

Addvilz commented Feb 14, 2018

Just a sidenote, using clusterize.js directly might not be possible, because clusterize.js is GPLv3.

@fergardi
Copy link

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?

@Addvilz
Copy link
Author

Addvilz commented Feb 15, 2018

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.

@stale
Copy link

stale bot commented Feb 18, 2019

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 stale bot added the stale label Feb 18, 2019
@Addvilz
Copy link
Author

Addvilz commented Feb 18, 2019

Pretty much actual still.

@stale
Copy link

stale bot commented Feb 18, 2020

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 stale bot added the stale label Feb 18, 2020
@Addvilz
Copy link
Author

Addvilz commented Feb 18, 2020

Why, hello there, stale bot.

@stale stale bot removed the stale label Feb 18, 2020
@stale
Copy link

stale bot commented Apr 28, 2022

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 stale bot added the stale label Apr 28, 2022
@Addvilz
Copy link
Author

Addvilz commented Apr 28, 2022

Stale bot, old friend! How have you been?

@stale stale bot removed the stale label Apr 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants