aviaAsset_avia-head-scripts and aviaAsset_avia-footer-scripts

So the base of the issue is that rows in the _options table that plugin/themes used to pull data out of object caching have grown to a site that is not conducive with the current MySQL and object caching configuration on WP Engine.

The specific rows in question are;
aviaAsset_avia-head-scripts
and
aviaAsset_avia-footer-scripts

So in seeking a goal, there are two inquiries about the software and how it interacts with these rows.

1. Can autoload for these rows be safely disabled without effecting the normal operations of the site? and;

2. Are there any steps can be taken to mitigate the row growing so large, or would regular maintenance of this row be expected if disable autoload is not advisable?

For optimal performance on WP Engine, autoloaded is advised to keep under 800kb, and in the case of both of these noted rows, they are over 5MB in total.