wp_options.idb growing very fast since last Enfold update

Hello there,

Since an Enfold upgrade back in February 2020, our web site partition is filling in very fast. We’ve suspected (and disabled then) MySQL logging, but finally found out that wp-options.idb is filling up very fast, due to some Avia modules.
Having a look at the wp_options table, here is what we get :

+————————————————–+————–+
| option_name | total_length |
+————————————————–+————–+
| aviaAsset_avia-head-scripts | 2063136 |
| aviaAsset_avia-footer-scripts | 1164868 |
| aviaAsset_css_filecontent | 527081 |
| aviaAsset_js_filecontent | 229771 |
| _transient_feed_0d2db5fea5a8633b56992c916819b198 | 202132 |
| _transient_feed_76f8d9281c01f21e505004d0986f50c6 | 121348 |
| ls-store-data | 26739 |
| avia_options_steelblue | 18231 |
| avia_options_enfold | 14484 |
| rewrite_rules | 12717 |
+————————————————–+————–+

You can check out also change of behaviour on this file : https://steel-blue.awsapps.com/workdocs/index.html#/share/document/fe57c4aa86262b96beec10f67090a1a6382578eee3f9ca7d531a44520a95e38d

Optomizing the table (OPTIMIZE TABLE wp_options;) has a direct effect (check out the drop on the graph on March. 2nd).

Can you please le tme know if there are actions to be taken there in order to fix this ?

Emmanuel