Huge cmplz_transients

I’m experiencing an issue with the cmplz_transients option on a large-scale news website. The site publishes a high volume of articles, and each article typically includes an embedded YouTube video. It appears that Complianz is storing preview data for every single YouTube video inside the cmplz_transients option. As a result, this option is growing to an extremely large size, which is starting to impact database performance. From what I can see, the transients contain cached YouTube preview data (thumbnails and related metadata), and they accumulate quickly due to the number of videos published. I’ve looked through the plugin settings but couldn’t find any way to: Limit the size or number of stored transients Disable this specific behavior for YouTube embeds Change how or where this data is stored Given the scale of the site, this is becoming a critical issue. Could you please advise: Is there a way to prevent Complianz from storing YouTube preview data in cmplz_transients ? Can this behavior be limited or filtered (e.g., via hooks or constants)? Are there recommended strategies for high-traffic / high-volume sites to avoid this database growth? If needed, I can provide more technical details or examples of the stored data. Thanks in advance for your help. Hi @stekky81 , Thanks for the detailed report. On a site publishing a lot of articles with embedded YouTube videos, this data can build up and start affecting database performance. We’ve logged this internally for our developers to investigate, so we can look at the best way to handle this for high-volume sites. I’ll keep this thread updated as we make progress. Thank you again for the report and for your patience. Best, Antonio