Title: Scalability issue
Last modified: August 20, 2016

---

# Scalability issue

 *  Resolved [htrex](https://wordpress.org/support/users/htrex/)
 * (@htrex)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/scalability-issue/)
 * Hello Tobias, as you’re refreshing your table plugin and maybe looking for new
   ideas I suggest to see this old thread where we where discussing about a problem
   that is present in this version too [http://wordpress.org/support/topic/plugin-wp-table-reloaded-table-edit-screen-crashes-a-chrome-tab-and-freezes-firefox](http://wordpress.org/support/topic/plugin-wp-table-reloaded-table-edit-screen-crashes-a-chrome-tab-and-freezes-firefox)
 * For this new plugin version maybe you can use pagination/caching/ajax loading
   technics so that it can scale to big tables at best, al least I hope for this
   nice plugin 😉
 * [http://wordpress.org/extend/plugins/tablepress/](http://wordpress.org/extend/plugins/tablepress/)

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Author [Tobias Bäthge](https://wordpress.org/support/users/tobiasbg/)
 * (@tobiasbg)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/scalability-issue/#post-3298511)
 * Hi,
 * thanks for your feedback!
 * Yes, this is a nagging and I would really like to fix it TablePress! Unfortunately,
   I haven’t yet found a good and easy implementation for this, yet 🙁
    Now, TablePress
   has made a lot of progress, in that the “Edit” screen is now no longer reloaded
   when changes are saved, as that is done via AJAX now. However, the initial load
   might still be slow with many textareas, and this might still cause issues in
   browsers.
 * Now, after seeing how cool the new Media Manager in WP 3.5 turned out, with just
   a JavaScript-based implementation, I’m currently looking into using a similar
   development model in TablePress. Hopefully, this will help to finally fix this
   issue in the future.
 * Even though I don’t have good news about this yet, I still hope that you like
   TablePress 🙂
 * Best wishes,
    Tobias
 *  Thread Starter [htrex](https://wordpress.org/support/users/htrex/)
 * (@htrex)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/scalability-issue/#post-3298517)
 * Hi Tobias,
    nice to hear from you again! mmm, look if this library could come
   in help for backend data editing: [http://jquery-datatables-editable.googlecode.com/svn/trunk/index.html](http://jquery-datatables-editable.googlecode.com/svn/trunk/index.html)
 * Another couple of ideas:
    * an ecologic improvement that shouldn’t result in 
   a drastic disruption for the current codebase is to implement a final render 
   caching layer, beeing the render an HTML fragment, a json data structure or whatever…
   looking at server load and client wait times seems that data is queried on the
   database and arranged in the HTML presentation every time, with RAM and CPU resources
   used even if data has not been changed from the last render…
 * * thinking of a possible ajaxification please consider to don’t disrupt the current
   frontend behaviour to have the data printed in HTML on the public site, as real
   HTML can be be good for SEO and a JS progressive enhancement is enough.
    Otherwise
   to eventually allow publishing huge tables on the public site an ajax chunked
   data loading could be a must, but on my tests up to about 25.000 rows HTML is
   still an alternative, please leave an option for it! 😉
 * Cheers for TablePress!
    –htrex;
 *  Plugin Author [Tobias Bäthge](https://wordpress.org/support/users/tobiasbg/)
 * (@tobiasbg)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/scalability-issue/#post-3298529)
 * Hi,
 * thanks for the link to the DataTables Editable script. I’m not yet sure that 
   this will work in TablePress, but I’ll check it out!
 * About the other two points:
    – TablePress does cache the final/rendered table
   HTML code, actually. (That’s on the frontend though, I don’t think that this 
   is helpful for the “Edit” screen.)
 * – 25.000 rows is really a lot. Have you thought about implementing this via a
   custom PHP/mySQL solution, where you directly use the AJAX loading methods that
   the DataTables library offers?
 * Best wishes,
    Tobias

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Scalability issue’ is closed to new replies.

 * ![](https://ps.w.org/tablepress/assets/icon.svg?rev=3192944)
 * [TablePress - Tables in WordPress made easy](https://wordpress.org/plugins/tablepress/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/tablepress/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/tablepress/)
 * [Active Topics](https://wordpress.org/support/plugin/tablepress/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/tablepress/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/tablepress/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [Tobias Bäthge](https://wordpress.org/support/users/tobiasbg/)
 * Last activity: [13 years, 5 months ago](https://wordpress.org/support/topic/scalability-issue/#post-3298529)
 * Status: resolved