Make WordPress Core

Opened 7 weeks ago

Closed 6 weeks ago

Last modified 5 weeks ago

#61764 closed defect (bug) (worksforme)

Site Health: Autoloaded options could affect performance

Reported by: 123nadav's profile 123nadav Owned by: mukesh27's profile mukesh27
Milestone: Priority: normal
Severity: normal Version: 6.6
Component: Site Health Keywords: close
Focuses: performance Cc:

Description

Hello guys how are you?

I notice from the new version of WordPress 6.6.1, the site health start to shows Autoloaded error.

Now, i checked the database with phpmyadmin and LS-CACHE Plugin (i have an openlitespeed server).

My Autoloaded list is not even 600kb (screenshot):

https://ibb.co/9HD3SQb

I look on the site health and in the link:

https://developer.wordpress.org/advanced-administration/performance/optimization/#autoloaded-options

Error should appear inside the SITE HEALTH when you have 1mb of Autoload tables.

I think we maybe have some bug here in the WordPress 6.6.1.

By the way:

I tried to delete plugin and turn off to remove the Autoload tables. but error still shows inside the Site Health section.

I open a ticket in the WordPress forum as well:
https://wordpress.org/support/topic/site-health-autoloaded-options-could-affect-performance/#post-17913920

Change History (14)

#1 follow-up: @mukesh27
7 weeks ago

  • Focuses performance added
  • Owner set to mukesh27
  • Severity changed from critical to normal
  • Status changed from new to assigned
  • Version changed from 6.6.1 to 6.6

Thanks @123nadav for the report. I will take a look. Thanks!

#2 in reply to: ↑ 1 @123nadav
7 weeks ago

Replying to mukesh27:

Thanks @123nadav for the report. I will take a look. Thanks!

Sorry but the version was change from 6.6 to 6.6.1
Just dont get confused it my mistake sorry.

#3 @mukesh27
7 weeks ago

@123nadav could you please share your site health check screenshot?

Have you clear server cache after removing the options? Please do it then check the site health again.

Last edited 7 weeks ago by mukesh27 (previous) (diff)

#4 @mukesh27
7 weeks ago

| Error should appear inside the SITE HEALTH when you have 1mb of Autoload tables.

That 1MB is the size of total autoloaded option value not the threshold (limit) for the autoload option, The threshold is 800kb.

I have tested and it working fine for me.

#5 @123nadav
7 weeks ago

As you see in my screenshot my Autoload is 635kb
https://imgbb.com/9HD3SQb

I have 3 identical websites its got triggered in all of them:
https://ibb.co/8D19W9c

By the way, I’ve removed plugins and reduced the autoload size even further below 623KB, yet it still shows a critical warning.

#6 @mukesh27
6 weeks ago

  • Keywords close added

Thanks @123nadav for the details.

Per https://ibb.co/8D19W9c it shows that 455 options are autoloaded and as per your DB screenshot it was 439 https://imgbb.com/9HD3SQb. The 16 options is not shows by your host that's why it shows the Site health notice.

Contact your host for more details.

#7 @123nadav
6 weeks ago

I am hosting my website myself on Google Cloud using an Ubuntu machine.
I can access phpMyAdmin and have deleted plugins, but nothing has helped.

Additionally, I deleted transients and revisions from the database, and now it's even smaller (619.41K). However, the Site Health section shows different information than what's in my actual database (447 AUTOLOAD OPTIONS VS 428 AUTOLOAD OPTIONS)

But even with more 19 autoload options, i dont believe you pass the 800kb...
Have a way to see the 19 autoloads Site Health read?

For the record:
I pretty sure is connected to "CORE" autoloads, this because this error raised up after the 6.6.1 WordPress update.

This ticket was mentioned in Slack in #core-performance by mukeshpanchal27. View the logs.


6 weeks ago

#9 @mukesh27
6 weeks ago

  • Milestone Awaiting Review deleted
  • Resolution set to worksforme
  • Status changed from assigned to closed

If you want to check the total options that are autoloaded in your database, run the following query (update the table prefix 'wp' as per your DB setup):

SELECT option_name, option_value FROM wp_options WHERE autoload IN ('yes', 'on', 'auto-on', 'auto')

https://ibb.co/YXR0Brb

Feel free to re-open if you have any questions.

#10 @123nadav
6 weeks ago

talked with LiteSpeed support and we checked the wp_options table. The database shows the autoload count is similar to the LiteSpeed plugin (426 autoloads).

The Site Health section shows 455, and this is not correct. Here are the screenshots:

It looks like the LS-CACHE plugin is correct:
https://ibb.co/TmY6bSg

I really don't know why the Site Health section shows 455:
https://ibb.co/B6gzF4p

Regards,
Nadav

#11 @mukesh27
5 weeks ago

@123nadav Update your DB query where clause WHERE autoload IN ('yes', 'on', 'auto-on', 'auto') you only check yes value.

[57920] for more details why the new value introduced in autoload. The Litespeed plugin needs to update that query too to get proper list for autoload options.

Last edited 5 weeks ago by mukesh27 (previous) (diff)

#12 @123nadav
5 weeks ago

OK, i tried your query in the console option inside phpmyadmin but anytime i get error:
https://ibb.co/QbgY4Lt

we try the first query it was working properly.

you maybe have idea? or a diffrent query i can put in the console option inside phpmyadmin?

#13 @mukesh27
5 weeks ago

@123nadav The issue comes from Litespeed plugin. I have open tracking issue for Litespeed plugin - https://github.com/litespeedtech/lscache_wp/issues/717

Please check it for more details.

#14 @123nadav
5 weeks ago

OK, thank you for opening this ticket in GitHub, by the way, i am with them on the support channel they have.

So please dont close this ticket @mukesh27
And thank you again for your time, appriciate that.

Note: See TracTickets for help on using tickets.