-
Posts
-
Hello,
Following this tutorial https://kinsta.com/knowledgebase/wp-options-autoloaded-data/ I found out that in our wp_option table aviaAsset_avia-head-scripts is using 5406068 kilobytes
executing:
SELECT ‘autoloaded data in KiB’ as name, ROUND(SUM(LENGTH(option_value))/ 1024) as value FROM wp_options WHERE autoload=’yes’
UNION
SELECT ‘autoloaded data count’, count(*) FROM wp_options WHERE autoload=’yes’
UNION
(SELECT option_name, length(option_value) FROM wp_options WHERE autoload=’yes’ ORDER BY length(option_value) DESC LIMIT 10)returns
autoloaded data in KiB
5932
autoloaded data count
2222
aviaAsset_avia-head-scripts
5406068
aviaAsset_js_filecontent
245742
option_tree_settings
35130
rewrite_rules
32480
avia_options_enfold-child
21200
wpseo_taxonomy_meta
17351
wp_user_roles
16267
avia_instagram_widgets_cache
16189
cron_projects
15950
aioseop_options
14763In attachment content of aviaAsset_avia-head-scripts and aviaAsset_js_filecontent
Is it not normal. What can I do? If I delete them they will be regenerated?Thank you
MauroHi,
That is quite huge. Are you sure it’s in Kilobit and not Bit?
Have you tried disabling the merged files timestamp from the Performance > File Compression settings? In the performance panel, enable or toggle the Show advanced options, then set the “Unique timestamp of merged files” to the second option.
These threads might be related if the server has object caching.
// https://kriesi.at/support/topic/still-massive-db-writes-issues-with-merged-js-and-css-w-w-o-object-caching/
// https://kriesi.at/support/topic/merged-styles-object-cache-using-redis/Best regards,
IsmaelHi,
I see a select with two options
“Add unique timestamps (= default)”
Disable adding unique timestamps
I set it to the second, and the huge value disappearedexecuting a second time the query after changing to ” Disable adding unique timestamps”
SELECT ‘autoloaded data in KiB’ as name, ROUND(SUM(LENGTH(option_value))/ 1024) as value FROM wp_options WHERE autoload=’yes’
UNION
SELECT ‘autoloaded data count’, count(*) FROM wp_options WHERE autoload=’yes’
UNION
(SELECT option_name, length(option_value) FROM wp_options WHERE autoload=’yes’ ORDER BY length(option_value) DESC LIMIT 10)
I see the result in attachment (before and after)
before https://imgur.com/9mg50Q9
after https://imgur.com/2hxLRwTthe threads indicated get really technical and don’t really like to get too much into it
Our server is Kinsta which use its own caching system and I don’t know if and how they use object caching.Now, after changing to “Disable adding unique timestamps”, our table wp_options passed, after optimizing it, from 13.9 MiB to 3.8 MiB
Our folder ../wp-content/uploads/dynamic_avia seems to have an ordinary size
Please see
Hi,
Thank you for the info.
The content is actually saved in a file inside the dynamic_avia folder. The database entry is only used to combine the content of the enqueued or registered scripts in the site, then the theme converts it to an actual JS file.
If you want to get rid of it, you have to disable JS compression in the Performance > File Compression panel, and use a plugin like Autoptimize instead.
Best regards,
IsmaelHi, thank you for the info
we already use Wp Rocket
We can than delete these records from the database after we disable JS compression?Thank you
MauroHi,
Yes, you can delete those entries. The theme will just regenerate them if you decided to use the default compression again. But of course creating a backup or a restore point first is always recommended whenever you need to do something in the database.
Thank you for your patience.
Best regards,
Ismael
- The topic ‘aviaAsset_avia-head-scripts in Table wp_options’ is closed to new replies.