Destroy table performance issues
Destroy table performance issues
bikai
Posts: 21Questions: 12Answers: 0
- My table has 100 rows and 200 coloums in one page, the 'destroy()' will cost almost 4s in Chrome. The whole page is blockd at that time.
- while rendering, the page is blockd too, i used
"deferRender": truealready.
how to make it faster or seems faster?
This discussion has been closed.
Answers
If you post a link to a test page showing the issue, I'd be happy to profile it and see where DataTables is spending the majority of the time in your table. I would however say, if you can avoid using destroy - do so. It is always going to hurt performance. If you have another option such as reusing the existing table, do so.
Allan
@allan I tested it that 200 colums with 100 rows in a page, render it will cost 4s and destroy it will cost more than 10s. all test are under the latest Chrome.
if the table's colums are not changed, i will reuse the same table object, but most of the time, the colums are different each time, so i
.dstroy()before create the table.do you have any advises in this situation?
Without a test case to profile there isn't much help I can offer I'm afraid. Also DataTables doesn't attempt to provide any virtual column support (like it does with rows) so there aren't any performance optimisations that can be made for large numbers of columns.
Allan