however I would wish to know if there’s a approach to stop them from entering into my database within the first place.
The one approach to stop expired transients ever being a factor is to by no means use them to start with.
Whenever you create a transient an possibility is created with a selected title. Finally that transients expiration date comes and it wants cleansing up, this may be automated and WordPress does this routinely. Your state of affairs occurs as a result of that automation is both disabled or unable to run.
Sadly, what you are asking for is the very factor you are making an attempt to keep away from, a clear up cron job of some type.
As for RSS feeds, you would not need this. Not caching the outcome would result in main efficiency losses. HTTP requests are a few of the slowest and most costly issues you are able to do in WordPress. This could even have important knock on results on in style plugins that fetch information and different RSS feeds, in addition to RSS widgets and RSS blocks.
As an apart, when you have an object cache, WP will attempt to use it as an alternative for transient storage, e.g. Redis or memcached. Redis/and so forth will auto-cleanup, and has its personal expired rubbish assortment processes too. This turns into extremely dependent in your server and software program although, and also you’re primarily buying and selling one set of issues for one more. It’s best to get a persistent object cache for those who can, however basic efficiency causes not transient cleanup.
