complex-table is taking lot of time to load if records are more say 100000. you can change the /mock/article.js const count = 100000 to replicate this issue.
On Mon 19 Nov, 2018, 7:32 AM 花裤衩***@***.***wrote: Because the mock here is pure front-end implementation. So 100000 pieces of data, it's going to take a lot of computing time. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1336 (comment)>, or mute the thread < https://github.com/notifications/unsubscribe-auth/AWQE1w9uCP8R84ZMux9ugF7MCTjrhBJJks5uwhFFgaJpZM4Yn5jW > .
4条答案
按热度按时间fcipmucu1#
Because the mock here is pure front-end implementation.
So 100000 pieces of data, it's going to take a lot of computing time.
falq053o2#
I have tried with real backend as well same time…
On Mon 19 Nov, 2018, 7:32 AM 花裤衩***@***.***wrote: Because the mock here is pure front-end implementation. So 100000 pieces of data, it's going to take a lot of computing time. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1336 (comment)>, or mute the thread < https://github.com/notifications/unsubscribe-auth/AWQE1w9uCP8R84ZMux9ugF7MCTjrhBJJks5uwhFFgaJpZM4Yn5jW > .
dohp0rv53#
Are you paging your table data?
Element-ui's table has performance issues with big-data rendering.
epggiuax4#
No its retrieving all the records. If we add pagination at api level then it will affect the search…
On Mon 19 Nov, 2018, 10:21 AM 花裤衩***@***.***wrote: Are you paging your table data? Element-ui's table has performance issues with big-data rendering. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1336 (comment)>, or mute the thread < https://github.com/notifications/unsubscribe-auth/AWQE1zKBtEALZmSYMnU8yzxF-f_DnUGXks5uwjjegaJpZM4Yn5jW > .