It’s as shown on the help section… database will (only) grow if you are minifying files with dynamic content, or with dynamic file names. If the content is dynamic and changing on every pageview, its minified as unique and stored, as it should. In that case, you will get a new minified file on every uncached pageview.
The options allow you to exclude them and have the plugin minify only the regular static files. Dynamic content cannot be minified, else it would minify on every page and slow things down.
During optimization with FVM you need to understand how optimization works and manually decide what to do with that type of content. It’s not plug and play, it’s a manual optimization plugin.
Thanks for your reply but I had no dynamic content or file names.
From WordPress update 5th September, dB went from 9.9Mb to 1.9Gb in 11 days.
No settings were changed. On the verge of the site coming down.
the query string (375711253) change on every pageview (just refresh and you can see it). https://i.imgur.com/65rE5re.png
The query string changing will not only prevent any minification from doing the intended optimization for these files (the minification always sees a different, new file) but it also prevents browser caching for those files (even without minification).
I suggest checking with your dev or perhaps the theme author (if it’s the original theme) on why they need dynamic query strings on those static files. Version numbers should be ideally tied to the plugin/theme version, not some random or other digit.