• Resolved arjunmurali1993

    (@arjunmurali1993)


    Hi,

    Over the last few months, I’ve noticed that the wp-content\cache\asset-cleanup\js folder increases to 25-30GB in size every few days. With no option other than to manually remove them via SSH, I keep a reminder to do this every two days. Otherwise, our server’s 40GB disk gets full and WordPress stops working due to lack of space (it happened once and we had to spend a couple of hours to bring the site back live).

    Ours is a live site getting a good amount of traffic each day, so I don’t want to make any breaking changes in the settings that would affect user experience. Is there any setting in Asset Cleanup that I can disable in order to stop the rapid increase in the number of files on the above-mentioned js folder?

    Looking forward to your help.

    Regards,
    Arjun

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

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author Gabe Livan

    (@gabelivan)

    @arjunmurali1993 I have a strong suspicion of why this caching directory fills up and I want to fix it for you. I believe the fact that the inline JS associated with some SCRIPT tags is generating unique code once on every page load, making the “combine JS” feature ineffective as new unique files (due to the unique content) have to be generated.

    I checked your website and it looks like you have deactivated this feature. Can you please send me your current “System Info” from “Tools” (plugin’s menu) so I can check what settings you’ve applied there. As it contains sensitive information, please send it privately via https://www.gabelivan.com/contact/

    Thread Starter arjunmurali1993

    (@arjunmurali1993)

    Hi Gabe,

    Thanks for the quick response. I’ve shared the details as suggested.

    Regards,
    Arjun

    I also had this problem, the site was about 500 MB and asset cache folder 14GB… No more asset cache.

    mlevison

    (@mlevison)

    Also having this problem – the site has a lot of categories. A site with maybe 0.3GB content had cache of 6GB until I cleared it.

    mlevison

    (@mlevison)

    …bonus a day after clearing the cache its back to a 1 GB.

    Plugin Author Gabe Livan

    (@gabelivan)

    @mlevison can you check /wp-content/cache/asset-cleanup/ and let me know which directory takes most of the space? I assume it’s the “js” one. Can you share the URL to your website here? If you’re not comfortable with that, you can reach me via https://www.gabelivan.com/contact/

    mlevison

    (@mlevison)

    Gabe – thanks – it is the JS folder as you guessed clocking in at a fat 1022MB right now. Site: https://yourfinanciallaunchpad.com

    Thanks for any hints
    Mark – mostly human

    mlevison

    (@mlevison)

    ….? and the magic secret incantation is?

    Cheers
    Mark

    Plugin Author Gabe Livan

    (@gabelivan)

    @mlevison if that’s the case it means that the inline code associated with the JS files is not included in the combined JS files (look for something like “fes_nonce” in the HTML source to understand what I mean) and in this, once the old caching is cleared (based on the setting you have in “Settings” -> “Plugin Usage Preferences” -> “Clear previously cached CSS/JS files older than (x) days“), the size of the directory will decrease in time.

    I’m considering lowering the 1 GB limit in time as I believe it’s too large. It’s enough if a few hundred MB is filled and it’s obvious that it’s very likely something is not right there and the files keep generating based on non-unique JavaScript code.

    mlevison

    (@mlevison)

    @gabelivan Danke. I set the rentention down to 4 days. Now the directory size varies from 100MB -> 1.1 GB. The upper end is a tab high but tolerable. Our server WPEngine has a limit of 20GB per account on our current plan, shared over all of our sites. This has taken care of that problem. – Mark

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘wp-content\cache\asset-cleanup\js folder Size Increasing very rapidly’ is closed to new replies.