Store Transients unexpected behavior

Hi,

On the doc page https://docs.litespeedtech.com/lscache/lscwp/cache/#store-transients it sais:

Enable Store Transients to get server notices when Cache WP Admin is disabled.

Which lead me to conclude that leaving it ON (the default), while also leaving the options Persistent Connection and Cache WP Admin ON (also default), would not hurt.

But this seems to happen:

Transients are still stored to the DB, but never get deleted again (I suppose because of the fact that they are deleted in the object cache) which causes the DB options table to grow out of proportions over time.

Specially when activating a “transient-heavy” plugin like Jetpack’s Stats module, the options table grows to over 2 Gigs in under two days.

Switching Store Transients OFF solves the issue.

Would it not be more logical to automate this feature, instead of leaving it up to the confused user? I mean: auto-off when Cache WP Admin is ON and auto-on when Cache WP Admin is OFF. Or at least, make the default settings not be so hurtful to the database? And maybe make the documentation a bit clearer about possible consequences of its setting?

Thanks 🙂

The page I need help with: [log in to see the link]