[ad_1]
The expired transients should be deleted automatically – that’s the reason why they have a expire date. I wonder why this does not happen automatically. I have to check this.
Is it possible to store them in a different table? my wp_options table was 10 pages long but now it’s 450 pages. Might be caused by WP 6.0 or a new plugin version because I never noticed this before.
Ok, I checked it in detail.
First of all – having transients at all is completely OK since the plugin uses transients to cache the image metdata for up to 24 hours to improve performance, so the metdata for images (size, EXIF data etc.) does not have to be determined with every page request.
If you have many images on your site, you may also have many transients since for each image one transients gets created if it is loaded. However, these transients should not cause any performance issue since they will not get loaded automatically due to their expiration date of about 24 hours after creation.
Furthermore Also expired transients will get cleaned up by WordPress automatically. If this does not work on your site you should check if cron jobs are executed properly on your site. If possible, you may disable the internal cron execution and use a dedicated job for that.
Also see:
Edit: you can also improve the performance by using a Redis database and Redis Object Cache – then all transients will be managed by Redis which can be much faster than a MySQL/MariaDB database.