Title: Mega cache problem Last modified: March 15, 2017 --- # Mega cache problem * Resolved [espacemusculation](https://wordpress.org/support/users/espacemusculation/) * (@espacemusculation) * [9 years, 7 months ago](https://wordpress.org/support/topic/mega-cache-problem/) * Hello all, Hello Franck * I have a question about cache, * Does the cache grow without limit ? * ![](https://i0.wp.com/img4.hostingpics.net/pics/592779Sanstitre3.jpg) * Can we limit the number of file ? 1 per page ? * I do not understand why there is so much file? I have just 300 pages. * Thanks you for your help Viewing 10 replies - 16 through 25 (of 25 total) [←](https://wordpress.org/support/topic/mega-cache-problem/?output_format=md) [1](https://wordpress.org/support/topic/mega-cache-problem/?output_format=md) 2 * Plugin Author [Frank Goossens](https://wordpress.org/support/users/futtta/) * (@futtta) * [9 years, 7 months ago](https://wordpress.org/support/topic/mega-cache-problem/page/2/#post-8920039) * you do have a _**huge**_ amount of inline CSS, is this an option somewhere? if you have less inline CSS, unchecking “also aggregate inline CSS” will not be frowned upon by GPSI? * > #execphp-xx is ok I know these id, they are fixed. * so are the same execphp-xx’s used in every page? and does it always have the same CSS applied? * > I test again without preload this time I will see tomorrow waking up * well, it will be a lot smaller, but ultimately it will grow and grow as well. preload as such is not the reason, it only makes the problem visible faster. * Thread Starter [espacemusculation](https://wordpress.org/support/users/espacemusculation/) * (@espacemusculation) * [9 years, 7 months ago](https://wordpress.org/support/topic/mega-cache-problem/page/2/#post-8920131) * Unfortunately the file number has increased overnight, up to about 1000 * Yes the same execphp-xx are used every page, it is the ID of my widgets. and it is the same css for all execphp * Plugin Author [Frank Goossens](https://wordpress.org/support/users/futtta/) * (@futtta) * [9 years, 7 months ago](https://wordpress.org/support/topic/mega-cache-problem/page/2/#post-8920367) * so quoting myself; * > you do have a huge amount of inline CSS, is this an option somewhere? if you > have less inline CSS, unchecking “also aggregate inline CSS” will not be frowned > upon by GPSI? * Thread Starter [espacemusculation](https://wordpress.org/support/users/espacemusculation/) * (@espacemusculation) * [9 years, 7 months ago](https://wordpress.org/support/topic/mega-cache-problem/page/2/#post-8920890) * I use Avada as a template that uses online Css for each “block” * If I disable this option I lose a big profit in the Google Pagespeed * Plugin Author [Frank Goossens](https://wordpress.org/support/users/futtta/) * (@futtta) * [9 years, 7 months ago](https://wordpress.org/support/topic/mega-cache-problem/page/2/#post-8921197) * > If I disable this option I lose a big profit in the Google Pagespeed * well, in general GPSI does not like it when there’s a lot of CSS inlined (it will complain about round-trip times to render the content). moreover that option is of no importance when using AO CSS optimization if you have “aggregate inline CSS” active anyhow. * so if I were you I would; * make sure all original css that _can_ be linked instead of inlined is moved out of your HTML * disable AO’s “also aggregate inline CSS” (to fix your cache-size problem) * optionally (once all works) experiment with “inline & defer CSS” * frank * Thread Starter [espacemusculation](https://wordpress.org/support/users/espacemusculation/) * (@espacemusculation) * [9 years, 7 months ago](https://wordpress.org/support/topic/mega-cache-problem/page/2/#post-8921388) * Thank you for trying to help me 🙂 * I just tested but that does not solve the problem. * I also just compare the css files and there is a css file for the mobile and another for the desktop. I think for the plugin, it creates indefinitely files because it thinks the source code changes? * Plugin Author [Frank Goossens](https://wordpress.org/support/users/futtta/) * (@futtta) * [9 years, 7 months ago](https://wordpress.org/support/topic/mega-cache-problem/page/2/#post-8922648) * > I think for the plugin, it creates indefinitely files because it thinks the > source code changes? * almost there, this is correct though; * > the plugin creates indefinitely files because the source code changes * -> if the (aggregated) source-code is identical, it does not create a new cached file. if the source-code is different (even just a space or comment), it does create a new file. * frank * Thread Starter [espacemusculation](https://wordpress.org/support/users/espacemusculation/) * (@espacemusculation) * [9 years, 7 months ago](https://wordpress.org/support/topic/mega-cache-problem/page/2/#post-8928829) * Hello Franck 🙂 * I hope you are well. * I found the solution to the problem. In fact I use the Avada theme which dynamically generates a bit of css. * In theme options, there is a page : Dynamic CSS & JS * CSS Compiling method Select “File” mode to compile the dynamic CSS to files ( a separate file will be created for each of your pages & posts inside of the uploads/fusion-styles folder), “Database” mode to cache the CSS in your database, or select “Disabled” to disable. * This option was disabled. I activated “file” and then everything came back in order. * A big thank you for your help and for this super plugin ! * Plugin Author [Frank Goossens](https://wordpress.org/support/users/futtta/) * (@futtta) * [9 years, 7 months ago](https://wordpress.org/support/topic/mega-cache-problem/page/2/#post-8929114) * that’s interesting information [@espacemusculation](https://wordpress.org/support/users/espacemusculation/), thanks for the feedback, sure others will find this useful as well! * bon weekend (beaucoup de pluie ici, mais soit 😉 )! frank * Thread Starter [espacemusculation](https://wordpress.org/support/users/espacemusculation/) * (@espacemusculation) * [9 years, 7 months ago](https://wordpress.org/support/topic/mega-cache-problem/page/2/#post-8929221) * with pleasure * thanks again * (le temps n’est pas super ici non plus 😉 ) * Jimmy Viewing 10 replies - 16 through 25 (of 25 total) [←](https://wordpress.org/support/topic/mega-cache-problem/?output_format=md) [1](https://wordpress.org/support/topic/mega-cache-problem/?output_format=md) 2 The topic ‘Mega cache problem’ is closed to new replies. * ![](https://ps.w.org/autoptimize/assets/icon-256X256.png?rev=2211608) * [Autoptimize](https://wordpress.org/plugins/autoptimize/) * [Frequently Asked Questions](https://wordpress.org/plugins/autoptimize/#faq) * [Support Threads](https://wordpress.org/support/plugin/autoptimize/) * [Active Topics](https://wordpress.org/support/plugin/autoptimize/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/autoptimize/unresolved/) * [Reviews](https://wordpress.org/support/plugin/autoptimize/reviews/) * 25 replies * 2 participants * Last reply from: [espacemusculation](https://wordpress.org/support/users/espacemusculation/) * Last activity: [9 years, 7 months ago](https://wordpress.org/support/topic/mega-cache-problem/page/2/#post-8929221) * Status: resolved