Thread Starter
ganaxi
(@ganaxi)
Just to add,
although I have a lot of CSS, just to be sure, I also tried deleting all of the custom CSS and re-ran, but I came about only 1+ sec less than the above times.
Hi,
from what I can see, the tables don’t really have that much of an influence on this particular speed test.
Of course, as the tables are rather big, with almost 3000 rows, they will account for some of the slowness, as the data simply needs to be transmitted from the server to the browser.
Additionally, the JavaScript functions (for sorting, etc.) just need time to process the table.
However (if I interpret that chart correctly), the transmission of the HTML is not the bottleneck though. The majority of the time is spent retrieving some data from a Twitter server.
So, unfortunately, I don’t really see things that could be optimized here in TablePress, sorry 🙁 If this really bugs you, you’ll need to look into a custom solution with a mySQL table for example, that then only loads the relevant entries to the page, and not all of them at once.
Regards,
Tobias
Thread Starter
ganaxi
(@ganaxi)
Thanks, Tobias.
I am not sure I fully understand the results from that test. However, from what I can tell, I loaded successive pages (all identical in terms of other elements, except for #rows in the Table). The pages as a whole increased incrementally almost from 3 sec for tables with <100 entries to the 8-10sec for 1000 entries to 12-15sec for 2000-2500 entries and then the 25-30sec I mentioned in the largest 4000+ entries Table.
The tests above are a bit tricky, for they tell me a different bottleneck everytime I remove something, and finally when all that is left on the page is the 4000+ entries table, it still shows up in the 25sec download time range.
While I am no expert at this, logically it leads me to think that the load times are related to TablePress, and the way it displays data in the browser.
That being said, I understand that this is probably not a common use for 4000+ rows by 10 columns of data, and I still will say TablePress is by far the best solution for most uses. For now, I am going to have to live with this limitation, but it affects probably only 5%-10% of the almost 800-1000 tables I have on my site.
Thanks, again, for a great plugin.
Ganaxi
Hi,
well, see, the main reason for this is the amount of data. The page that you linked to is almost one megabyte in size, and transferring that from the server to the browser just takes time. And then the browser has to render everything, which again takes time.
This is however not related to how TablePress “displays” the data, because TablePress doesn’t do any of that. TablePress just generates the HTML code for a table, the server transfers that to the browser, and the browser has to interpret the code and render it as a table. This would be the same as if you had hand-coded the table’s HTML code into the page.
Of course, the server needs some processing time to generate the code, and also to load everything from the database, before anything is transmitted. This can indeed be influenced by the number of plugins, and by the separation into WP-Table Reloaded/TablePress, but I guess we have no way around this.
So, for now, you’ll indeed have to live with this.
Regards,
Tobias
