Autoloaded Options

  • Hi everybody,

    website status report shows me that the size of autoloaded options is too big. I′ve read some raised topics and have seen, that one can change this 800 kb size, that has been defined automatically. But I would rather clean up some space by throughing away the options that are not needed any more or setting autoload on off or no, where it makes sense. The problem is, that I do not have the technical information to understand the list of the autoloaded options and don′t know what each option referrs to; if it might be deactivated. Could someone assist me to understand the logic and get to know, if there are options that should be left on auto or options that could be deleted or set on off?

    Thanks in advance.

    The page I need help with: [log in to see the link]

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

  • The message concerns the database table options, which is used by WordPress. Individual entries in the table have a very high value in themselves and are automatically loaded each time the page is called up. The background is described here in a very technical form: https://make.www.ads-software.com/core/2024/06/18/options-api-disabling-autoload-for-large-options/

    You have 3 options:
    a) You check which component of your project leaves such large data records in the options table. This could be difficult to find. A look at the data records in SQL would be most suitable, if you are able to do so.
    b) You can use a PHP hook to increase the threshold value for the warning. This would stop it from being displayed. Details are described in the link above.
    c) You ignore the warning. It is primarily intended to alert you to a possible error.

    Thread Starter msezavar

    (@msezavar)

    Hi @threadi

    thanks for your comment. I took a look into the data records and found some entries with big data size. Of course, I don′t know how “large” a record might be and still considered as “normal” or OK. Anyways, the largest record is wp_postmeta with 228.6 Mib. After that wp_post with 73.1, wp_rcb_consent with 20.1 and wp_rcb_template with 15.6 Mib. Is that considered to be normal?

    Best

    The message is not about the database tables such as wp_post or wp_postmeta but about data records within the wp_options table. There it is about the option_value column.

    Thread Starter msezavar

    (@msezavar)

    Oh, sorry, misunderstanding. I now took a look at the wp_options table and the records in it. I sorted the option_value column descending. I thought, in the wp_option table there would be also a column showing how large each data record is. Here I have lots of records with option_name and option_value, but I don′t know how large each record is. I just trusted that the records would be sorted descending in size. The records in the very first pages are mostly about our cookie banner. I don′t think that I would want to deactivate auto-upload here.

    I don’t know which interface you have and what the sorting function there does for you. Normally (as with phpmyadmin) columns in such interfaces are sorted by alphabet.

    If you want to sort by size, you have to write an SQL query yourself. Example:

    select LENGTH(option_value) as mylength,option_value, option_name from wp_options order by LENGTH(option_value) desc

    The alternative to all of the above is that you can also ignore this. It’s just a warning that WordPress sets because it could affect loading times.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.