I hope I did not miss a post relating to this topic.
I imported csv data (1250 rows x 12 columns) and when I select a table to edit, the web page becomes unresponsive for 30 secs, and even after the table has loaded, scrolling down the table using chrome's scroll bar is very slow. (My computer: AMD 64 Athlon X2 2.8GHz dual core.)
I created an application to pull the data from this table and display it in a table... nothing fancy, just a display table using the following function:
$table = TablePress::$controller->model_table->load( 9 );
This data I load into a JS variable, and subsequently generate a table. In my case I hide the table and once it is filled I display the rows.
It takes < 1 sec to get the table data from the server into the JS variable, and about 3 secs to display the whole table.
I ran the Tablepress edit page with Chrome's 'Timeline' profiler turned on, and I saw many layout events with a note from Chrome saying:
"Forced synchronous layout is a possible performance bottleneck."
After plugging this note into google, I found this article about triggering layout events in the browser:
I think Tablepress is making too many demands on the DOM in a short period of time, and of course, the DOM is *the* performance weak point.
Question: In the Tablepress edit mode, do you draw the table with server side code (php) or do you draw the table with JS? I'd be interested in looking at this code more closely. Can you point me to that section of the Tablepress code?