• Excellent plugin.

    How can I further speed up the loading of tables (I have lots of them in each post!) Is there a field in wp_options that I should create an index? Any other trick? Please advise.

    Also, a couple of suggestions to consider for the next release:
    1. The old wp_table plugin link was located under “Posts” and makes it faster to access when editing posts. Maybe move wp-table_reloaded there instead of “Tools”?

    2. The List of Tables takes too long to load when a blog has a couple of thousand tables. Please consider allowing the user to only load the most recent, say 100 tables, starting with the newest at the top (or allow user to customize how to view)!

    3. When I go to the plugin, it is because I want to import a table (mostly) not to see what tables are there. What if the tab that shows first by default is “Import a Table”, rather than “List Tables”?

    Thank you again for your hard work to make it so neat!

    https://www.ads-software.com/extend/plugins/wp-table-reloaded/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Hi,

    thanks for your questions!

    There is no need to add an index to the wp_options table. WP is usually very smart with its database scheme, so there should already be one on the name.
    Do you have any specific hints that the database select query on this table is slow?

    Your other questions:
    1) I won’t move it away from “Tools” for now (because many, many people are used to it now). But there will be an option to make it a top level menu item (basically equally to “Tools” or “Posts”). If I have time left, I’ll try to add a possibibility to move it to “Posts”.

    2) The next version will ship a new sorting script which should also speed the section you mention on the “List of Tables”. If that still doesn’t help, I’ll think about other possibilities.

    3) Same answer as for the first question: I can’t change it by default, because everybody (besides you ?? ) will be confused. But I’ll check if I can add a plugin filter which would allow you to set the default screen for the first view.

    Best wishes,
    Tobias

    Thread Starter daskas

    (@daskas)

    Tobias,

    Thank you for the answers. Regarding the index in the wp_options table, yes, there is one for the option_name field, and it will be OK if that is all you are using to access the table.

    What I am wondering about is if I should add any other index on any OTHER field that you may be using to access the wp_options table of the WordPress DB, so that I make the access faster.

    Are you just using the option_name field? Any other field you may be using?

    Also, on a different subject, do you foresee any issue with WordPress overall slowdown in cases like mine, where I have hundreds of tables used (and probably several thousand more to be added over the next months) and stored in the wp_options table?

    Hi,

    I don’t think, there’s a need for another index on another field. I use the standard functions “get_option( $option_name )” provided by WordPress, so as far as I know that only uses the option_name field on which an index is set.

    For your second question: I don’t have any experience or user reports on using several thousand tables, so I can’t really tell if it will slow down WP.
    I used the wp_options table to be a little bit more independent from creating own DB tables, which is kind of messy and only clutters the DB for people with only few tables. If you have several thousand though, I would recommend using a separate DB table for those, because in that case the wp_options table would just grow too large.
    Currently using your own DB table is not implemented but should be easily possible by writing new functions for “get_option” or “update_option”.
    Before that is added I would recommend setting the “autoload” value in the wp_options table to “false” for all rows related to WP-Table Reloaded (Currently all tables are loaded on each run of WP, to save DB queries, but for many tables this is probably not so good, because you don’t need all of them at the same time.)

    Regards,
    Tobias

    Thread Starter daskas

    (@daskas)

    Thank you Tobias. I appreciate the pointer you provided regarding the “autoload” field. I run an UPDATE query and I set it to “no” for older tables so that they do not ALL load in memory, just the most recent ones will load.

    I’ll run the query every 1-2 months.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘[Plugin: WP-Table Reloaded] Speed Up Table Loading Further’ is closed to new replies.