Home > front end >  Table data volume is too big, too many columns, which leads to the rendering too slow, is there any
Table data volume is too big, too many columns, which leads to the rendering too slow, is there any

Time:10-09

Seems to be very slow, in the IE and chrome, have what good method to optimize,
Take data through ajax, once found this page shows all the data sent to the browser

CodePudding user response:

2 pages bai ~ ~ ~

CodePudding user response:

Paging is better, if there are 10000 records, assuming that the table has five columns, then 10000 records to produce at least 50000 dom node, at that time, the fairy will not save to save the browser,
Using ajax, if you don't have a clean up before the display of data, that will eventually lead to the problems above

CodePudding user response:

The dom have SiWuWanGe indeed

CodePudding user response:

Paging!
The screen only so big, the data is beyond your screen can't see the
Tens of thousands of lines of data at a time, no one will see

CodePudding user response:

You can use the bootstrap grid system to do the layout,

CodePudding user response:

Paging so much data see people also have a headache

CodePudding user response:

Paging,,,,,,,,,,,,,,,,,,

CodePudding user response:

Considering the paging display

CodePudding user response:

Said the paging to scheme, paging by what? The second page of the leaf node root on the first page?

CodePudding user response:

The best way to take child nodes are dynamic, anyone can use, for example,

CodePudding user response:

You first need to determine exactly which slow
TTFB time is too long, it needs to query methods to optimize the background
Data transmission time is too long, loading step by step,,,

CodePudding user response:

Not only paging method, can consider to use "virtual dom infinite rolling load"!

CodePudding user response:

One-time to obtain the data for the list, and then to paging the list, you can according to the pageSize a show, for example, according to the length of the list for total number of pages is remainder pages + 1, each click, all data to the corresponding page in the list out of the list. The slice ((currentPage - 1) * pageSize, currentPage * pageSize)

CodePudding user response:

https://github.com/livelyPeng/pl-table smoothly render all level data will not affect the element - UI el - table component of the original function, and added some function

CodePudding user response:

https://github.com/livelyPeng/pl-table smoothly render all level data will not affect the element - UI el - table component of the original function, and added some function

CodePudding user response:

https://github.com/livelyPeng/pl-table smoothly render all level data will not affect the element - UI el - table component of the original function, and added some function

CodePudding user response:

Thinking is very nice but I want to use the scroll bar is browser with scroll bar
  • Related