So i have this warmer in the WP dashboard in Site Health
Autoloaded options are configuration settings for plugins and themes that are automatically loaded with every page load in WordPress. Having too many autoloaded options can slow down your site. Your site has 2382 autoloaded options (size: 3 MB) in the options table, which could cause your site to be slow. You can review the options being autoloaded in your database and remove any options that are no longer needed by your site.
After looking in the options table i have large amounts of aws_search_term_** files.
Any reason why they are they and how to remove them?
Thanks
updraft_lock_wpo_wcpdf_main_semaphore_lock_order_20329_email_customer_completed_order
updraft_lock_wpo_wcpdf_main_semaphore_lock_order_20329_email_customer_processing_order
updraft_lock_wpo_wcpdf_main_semaphore_lock_order_20329_email_new_order
Is this a new feature? Can these entries be removed safely? As this is substantially polluting the options table.
]]>echo get_option($GLOBALS['SHORTNAME'].'_instagram_link','');
The trouble is I can’t find where these would have been entered into the options table from. The links are not in the links section of my admin and there doesn’t seem to be a widget for this. I did this so long ago I can’t remember how I did it. Is it possible that these could have been added to options via a plugin and if so does anyone know what plugin this might be as I don’t have a plugin installed that currently does this?
Many thanks.
]]>Under ‘Other Options’, I’ve tried all 3 experimental features. I’ve enabled and disabled PHP CLI checking. I’ve adjusted the ‘Queries per batch’, using values ranging from 200 through 1536. I’ve enabled and disabled SQL-Splitting.
In my .htaccess I’ve increased my ‘max_execution_time’ as follows:
php_value max_execution_time 300
In my wp-config, I’ve increased both my ‘WP_MEMORY_LIMIT’ and ‘WP_MAX_MEMORY_LIMIT’ to 1024MB. I also enabled ‘WP_DEBUG’ to see if there are any error messages.
I’m hoping you can provide some direction.
The following is a copy of my log file:
[STEP] [2022-03-30 06:09:16] Initializing restore process
[STEP] [2022-03-30 06:09:18] Looking for PHP CLI executable file.
[INFO] [2022-03-30 06:09:18] PHP CLI Filename: php
[INFO] [2022-03-30 06:09:18] PHP CLI Version: 7.4.28 (cli)
[INFO] [2022-03-30 06:09:18] PHP CLI Memory limit: 1024M/512M
[INFO] [2022-03-30 06:09:18] PHP CLI Execution limit: 0/0
[SUCCESS] [2022-03-30 06:09:18] We properly detected PHP CLI executable file.
[SUCCESS] [2022-03-30 06:09:19] PHP CLI: Restore process initialized, restoring...
[SUCCESS] [2022-03-30 06:09:19] Restore process responded
[SUCCESS] [2022-03-30 06:09:19] Locking migration process
[STEP] [2022-03-30 06:09:19] Initializing restore process
[INFO] [2022-03-30 06:09:19] Backup & Migration version: 1.1.9
[INFO] [2022-03-30 06:09:19] Initializing custom error handler
[INFO] [2022-03-30 06:09:19] Site which will be restored: ***site_url***
[INFO] [2022-03-30 06:09:19] PHP Version: 7.4.28
[INFO] [2022-03-30 06:09:19] WP Version: 5.9.2
[INFO] [2022-03-30 06:09:19] Web server: Not available
[INFO] [2022-03-30 06:09:19] Max execution time (in seconds): 259200
[SUCCESS] [2022-03-30 06:09:19] Restore process initialized successfully.
[STEP] [2022-03-30 06:09:19] Free space checking...
[INFO] [2022-03-30 06:09:19] Checking if there is enough amount of free space
[INFO] [2022-03-30 06:09:19] Requires at least 157760271 bytes. [150.45 MB]
[INFO] [2022-03-30 06:09:19] Disk free space function is not disabled - using it...
[INFO] [2022-03-30 06:09:19] Checking this path/partition: ***ABSPATH***/wp-content/***backup_path***/backups
[SUCCESS] [2022-03-30 06:09:19] There is 1,943,686.06 MB free. [1.85 TB]
[SUCCESS] [2022-03-30 06:09:19] Great! We have enough space.
[SUCCESS] [2022-03-30 06:09:19] Confirmed, there is enough space on the device, checked: 157760271 bytes.
[INFO] [2022-03-30 06:09:19] Making temporary directory
[STEP] [2022-03-30 06:09:19] Scanning archive...
[INFO] [2022-03-30 06:09:19] Scan found 3469 files inside the backup.
[STEP] [2022-03-30 06:09:19] Smart memory calculation...
[INFO] [2022-03-30 06:09:19] There is 1024 MBs of memory to use
[SUCCESS] [2022-03-30 06:09:19] Setting the safe limit to 182 MB
[STEP] [2022-03-30 06:09:19] Extracting files into temporary directory (this process can take some time)...
[SUCCESS] [2022-03-30 06:09:22] Files extracted...
[STEP] [2022-03-30 06:09:22] Saving wp-config file...
[SUCCESS] [2022-03-30 06:09:22] File wp-config saved
[STEP] [2022-03-30 06:09:22] Getting backup manifest...
[SUCCESS] [2022-03-30 06:09:22] Manifest loaded
[INFO] [2022-03-30 06:09:22] Backup Migration version used for that backup: 1.1.5
[STEP] [2022-03-30 06:09:22] Restoring files (this process may take a while)...
[SUCCESS] [2022-03-30 06:09:24] All files restored successfully.
[STEP] [2022-03-30 06:09:24] Converting database files into partial files.
[INFO] [2022-03-30 06:09:24] Max rows per query (this site): 1536
[INFO] [2022-03-30 06:09:24] Unknown query output value of backup file, maybe it was made before v1.1.7
[INFO] [2022-03-30 06:09:24] Starting conversion of: pvdj_commentmeta table.
[INFO] [2022-03-30 06:09:24] Finished part 1 of pvdj_commentmeta table.
[SUCCESS] [2022-03-30 06:09:24] Finished 1/20 (5.00%): pvdj_commentmeta table, total of 1 parts.
[INFO] [2022-03-30 06:09:24] Starting conversion of: pvdj_comments table.
[INFO] [2022-03-30 06:09:24] Finished part 1 of pvdj_comments table.
[INFO] [2022-03-30 06:09:24] Finished part 2 of pvdj_comments table.
[SUCCESS] [2022-03-30 06:09:24] Finished 2/20 (10.00%): pvdj_comments table, total of 2 parts.
[INFO] [2022-03-30 06:09:24] Starting conversion of: pvdj_links table.
[INFO] [2022-03-30 06:09:24] Finished part 1 of pvdj_links table.
[SUCCESS] [2022-03-30 06:09:24] Finished 3/20 (15.00%): pvdj_links table, total of 1 parts.
[INFO] [2022-03-30 06:09:24] Starting conversion of: pvdj_litespeed_url table.
[INFO] [2022-03-30 06:09:24] Finished part 1 of pvdj_litespeed_url table.
[SUCCESS] [2022-03-30 06:09:24] Finished 4/20 (20.00%): pvdj_litespeed_url table, total of 1 parts.
[INFO] [2022-03-30 06:09:24] Starting conversion of: pvdj_litespeed_url_file table.
[INFO] [2022-03-30 06:09:24] Finished part 1 of pvdj_litespeed_url_file table.
[SUCCESS] [2022-03-30 06:09:24] Finished 5/20 (25.00%): pvdj_litespeed_url_file table, total of 1 parts.
[INFO] [2022-03-30 06:09:24] Starting conversion of: pvdj_loginizer_logs table.
[INFO] [2022-03-30 06:09:24] Finished part 1 of pvdj_loginizer_logs table.
[SUCCESS] [2022-03-30 06:09:24] Finished 6/20 (30.00%): pvdj_loginizer_logs table, total of 1 parts.
[INFO] [2022-03-30 06:09:24] Starting conversion of: pvdj_options table.
[INFO] [2022-03-30 06:09:24] Finished part 1 of pvdj_options table.
[INFO] [2022-03-30 06:09:25] Finished part 2 of pvdj_options table.
[SUCCESS] [2022-03-30 06:09:25] Finished 7/20 (35.00%): pvdj_options table, total of 2 parts.
[INFO] [2022-03-30 06:09:25] Starting conversion of: pvdj_postmeta table.
[INFO] [2022-03-30 06:09:25] Finished part 1 of pvdj_postmeta table.
[INFO] [2022-03-30 06:09:26] Finished part 2 of pvdj_postmeta table.
[INFO] [2022-03-30 06:09:28] Finished part 3 of pvdj_postmeta table.
[SUCCESS] [2022-03-30 06:09:28] Finished 8/20 (40.00%): pvdj_postmeta table, total of 3 parts.
[INFO] [2022-03-30 06:09:28] Starting conversion of: pvdj_posts table.
[INFO] [2022-03-30 06:09:28] Finished part 1 of pvdj_posts table.
[INFO] [2022-03-30 06:09:51] Finished part 2 of pvdj_posts table.
[SUCCESS] [2022-03-30 06:09:51] Finished 9/20 (45.00%): pvdj_posts table, total of 2 parts.
[INFO] [2022-03-30 06:09:51] Starting conversion of: pvdj_sbi_instagram_feed_locator table.
[INFO] [2022-03-30 06:09:51] Finished part 1 of pvdj_sbi_instagram_feed_locator table.
[SUCCESS] [2022-03-30 06:09:51] Finished 10/20 (50.00%): pvdj_sbi_instagram_feed_locator table, total of 1 parts.
[INFO] [2022-03-30 06:09:51] Starting conversion of: pvdj_sbi_instagram_feeds_posts table.
[INFO] [2022-03-30 06:09:51] Finished part 1 of pvdj_sbi_instagram_feeds_posts table.
[SUCCESS] [2022-03-30 06:09:51] Finished 11/20 (55.00%): pvdj_sbi_instagram_feeds_posts table, total of 1 parts.
[INFO] [2022-03-30 06:09:51] Starting conversion of: pvdj_sbi_instagram_posts table.
[INFO] [2022-03-30 06:09:51] Finished part 1 of pvdj_sbi_instagram_posts table.
[SUCCESS] [2022-03-30 06:09:51] Finished 12/20 (60.00%): pvdj_sbi_instagram_posts table, total of 1 parts.
[INFO] [2022-03-30 06:09:51] Starting conversion of: pvdj_swift_performance_image_optimizer table.
[INFO] [2022-03-30 06:09:51] Finished part 1 of pvdj_swift_performance_image_optimizer table.
[INFO] [2022-03-30 06:09:54] Finished part 2 of pvdj_swift_performance_image_optimizer table.
[SUCCESS] [2022-03-30 06:09:54] Finished 13/20 (65.00%): pvdj_swift_performance_image_optimizer table, total of 2 parts.
[INFO] [2022-03-30 06:09:54] Starting conversion of: pvdj_swift_performance_warmup table.
[INFO] [2022-03-30 06:09:54] Finished part 1 of pvdj_swift_performance_warmup table.
[INFO] [2022-03-30 06:09:54] Finished part 2 of pvdj_swift_performance_warmup table.
[SUCCESS] [2022-03-30 06:09:54] Finished 14/20 (70.00%): pvdj_swift_performance_warmup table, total of 2 parts.
[INFO] [2022-03-30 06:09:54] Starting conversion of: pvdj_term_relationships table.
[INFO] [2022-03-30 06:09:54] Finished part 1 of pvdj_term_relationships table.
[INFO] [2022-03-30 06:09:54] Finished part 2 of pvdj_term_relationships table.
[SUCCESS] [2022-03-30 06:09:54] Finished 15/20 (75.00%): pvdj_term_relationships table, total of 2 parts.
[INFO] [2022-03-30 06:09:54] Starting conversion of: pvdj_term_taxonomy table.
[INFO] [2022-03-30 06:09:54] Finished part 1 of pvdj_term_taxonomy table.
[INFO] [2022-03-30 06:09:54] Finished part 2 of pvdj_term_taxonomy table.
[SUCCESS] [2022-03-30 06:09:54] Finished 16/20 (80.00%): pvdj_term_taxonomy table, total of 2 parts.
[INFO] [2022-03-30 06:09:54] Starting conversion of: pvdj_termmeta table.
[INFO] [2022-03-30 06:09:54] Finished part 1 of pvdj_termmeta table.
[SUCCESS] [2022-03-30 06:09:54] Finished 17/20 (85.00%): pvdj_termmeta table, total of 1 parts.
[INFO] [2022-03-30 06:09:54] Starting conversion of: pvdj_terms table.
[INFO] [2022-03-30 06:09:54] Finished part 1 of pvdj_terms table.
[INFO] [2022-03-30 06:09:54] Finished part 2 of pvdj_terms table.
[SUCCESS] [2022-03-30 06:09:54] Finished 18/20 (90.00%): pvdj_terms table, total of 2 parts.
[INFO] [2022-03-30 06:09:54] Starting conversion of: pvdj_usermeta table.
[INFO] [2022-03-30 06:09:54] Finished part 1 of pvdj_usermeta table.
[INFO] [2022-03-30 06:09:54] Finished part 2 of pvdj_usermeta table.
[SUCCESS] [2022-03-30 06:09:54] Finished 19/20 (95.00%): pvdj_usermeta table, total of 2 parts.
[INFO] [2022-03-30 06:09:54] Starting conversion of: pvdj_users table.
[INFO] [2022-03-30 06:09:54] Finished part 1 of pvdj_users table.
[INFO] [2022-03-30 06:09:54] Finished part 2 of pvdj_users table.
[SUCCESS] [2022-03-30 06:09:54] Finished 20/20 (100.00%): pvdj_users table, total of 2 parts.
[SUCCESS] [2022-03-30 06:09:54] Database convertion finished successfully.
[STEP] [2022-03-30 06:09:54] Calculating new query size and counts.
[SUCCESS] [2022-03-30 06:09:54] Calculaion completed, printing details.
[INFO] [2022-03-30 06:09:54] Total queries to insert after conversion: 160
[INFO] [2022-03-30 06:09:54] Partial files count after conversion: 32
[INFO] [2022-03-30 06:09:54] Total size of the database: 5.64 MB
[INFO] [2022-03-30 06:09:54] Table count to be imported: 20
[STEP] [2022-03-30 06:09:54] Checking the database structure...
[INFO] [2022-03-30 06:09:54] Successfully detected backup created with V2 engine, importing...
[STEP] [2022-03-30 06:09:54] Restoring database...
[INFO] [2022-03-30 06:09:54] Initializing database import V2 engine...
[SUCCESS] [2022-03-30 06:09:54] Initialized successfully, memory usage: 32.07 MB
[INFO] [2022-03-30 06:09:54] Loading file list...
[SUCCESS] [2022-03-30 06:09:54] File list loaded, memory usage: 32.07 MB
[INFO] [2022-03-30 06:09:54] Restoring tables using temporary name...
[INFO] [2022-03-30 06:09:54] Finished 5/160 (3.13%) for pvdj_commentmeta table (part: 1/1, size: 909 B).
[INFO] [2022-03-30 06:09:54] Finished 10/160 (6.25%) for pvdj_comments table (part: 1/2, size: 1.84 KB).
[INFO] [2022-03-30 06:09:54] Finished 15/160 (9.38%) for pvdj_comments table (part: 2/2, size: 1.16 KB).
[INFO] [2022-03-30 06:09:54] Finished 20/160 (12.50%) for pvdj_links table (part: 1/1, size: 1.46 KB).
[INFO] [2022-03-30 06:09:54] Finished 25/160 (15.63%) for pvdj_litespeed_url table (part: 1/1, size: 848 B).
[INFO] [2022-03-30 06:09:54] Finished 30/160 (18.75%) for pvdj_litespeed_url_file table (part: 1/1, size: 1.02 KB).
[INFO] [2022-03-30 06:09:54] Finished 35/160 (21.88%) for pvdj_loginizer_logs table (part: 1/1, size: 817 B).
[INFO] [2022-03-30 06:09:54] Finished 40/160 (25.00%) for pvdj_options table (part: 1/2, size: 954 B).
[DOWNLOAD GENERATED] File downloaded on (server time): 2022-03-30 06:15:38
[DOWNLOAD GENERATED] Last update (seconds): 344 seconds ago
[DOWNLOAD GENERATED] Last update (date): 2022-03-30 06:09:54
]]>Is it possible to include the options table?
All my content added through an options table are not indexed, and this is what ACF support said:
“ACF field values are not searchable by default which could suggest that the search plugins that you are using are only querying values in the posts and postmeta table. Options field values on the other hand are saved on the options table and thus I can suggest that you get in touch with the author of ACF better search so that they can advise on how to extend the search to the options table.”
Thank you
]]>I was wondering why the row ws_menu_editor_pro in wp_options table takes 90% of the total size of the table?
I always clean my options table through mySQL directly to keep it optimised and wordpress running quickly but obviously having 1 single row in the options table taking up 90% of the total size is odd. its 0.5 MB
Could you explain the reasons why this is the case?
Thanks
]]>Any suggestions?
]]>We are assuming this is a core wordpress issue.
Repeated update on “options” table ‘WHERE ‘Option_name’ = ‘Rewrite_rules’ – This update is happening on each and every page load thereby increasing the load on DB CPU. Please let us know if this is the default WordPress behavior and how to get rid of this query or mitigate it.
Here is the query which is causing trouble:
UPDATE cms_options
SET option_value
= ‘{{Data volume around 0.5MB}}’
WHERE option_name
= ‘rewrite_rules’
Regards,
Sujit