It’s common for that option to get pretty big if you have a lot of admin menu items and/or lots of custom settings like custom colors for each item, complex role permissions, and so on. The configuration data is stored in a format that’s good for quick parsing but not very efficient in terms of space.
It’s safe to disable autoload. However, the plugin will still try to load the option at least on every admin page, which means one additional SQL query per page load.
Another thing you could try is to enable this feature in the “Settings” tab:
“Compress menu configuration data that’s stored in the database ”
Then go back to the “Admin Menu” tab and click “Save Changes” (you don’t need to actually change anything there). This should significantly decrease the size of the ws_menu_editor
option. The drawback is that the plugin will have to spend more time per page load on decompressing the configuration data. I would recommend running some benchmarks before and after enabling this feature to see if it actually helps or hurts performance.
-
This reply was modified 4 years, 5 months ago by Janis Elsts. Reason: Fixed spelling