Hello @ipstenu ,
This is just to let you know, we have released an update where we have fixed the problem. We have regenerate assets option to clear all files.
Can you please update the plugin to the latest version i.e. 1.23.0?
Let me know how it goes.
Regards,
Sweta
I read through the changelog and I don’t think this will fix it in the long run.
Once they hit a certain number of files, the operating system will roll over and die. You can’t even really do it by age since if a site has enough pages/posts/cpts and enough traffic, it’ll generate more and more. Plus if you have too many already, you won’t be able to get PHP to delete them all (try it on 10,000-100,000 files yourself, and watch things grind).
That’s why a lot of hosts limit files (i.e. how many you can have per folder). And that’s also why many cache plugins break apart things into folders like this:
- /wp-content/uag-plugin/cache/PAGENAME/file.css
- /wp-content/uag-plugin/cache/PAGENAME/file.js
I’ve updated the site and warned the customer that this may not work given their site size (it’s exceptionally large)
Hello @ipstenu ,
In our v1.23.0 we have improved our file generation logic.
Now, We replace the old assets files for a particular Post/Page with the new files when Post/Page gets updated instead of adding new files each time.
So for a Single Page/Post, there will be at most 2 files ( One CSS & One JavaScript file ).
So there will be no load on the user’s site.
Also, we have provided an option to “Regenerate Assets” in plugins settings, which deletes all the old assets files & new ones are created when the Post/Page is reloaded.
Also, We will also check what we can do to break files into multiple folders.
Thank you for your suggestions!
Hope the above information helps.
Regards,
Rajkiran
I’ll test it out and have the customer test it at scale.
I will note, you’re confusing a couple things.
So for a Single Page/Post, there will be at most 2 files ( One CSS & One JavaScript file ).
So there will be no load on the user’s site.
Yeah that’s not what I care about right now 😀 I care that with 100,000 unchecked files being generated, it bogs down the server, which absolutely bolloxes the user’s site.
2 files per page. Say 10,000 pages on a site? 20,000 files. That slows things down when you, say, run a server backup.
For an example here, on Windows, they say never have more than 5000 files in a folder. With XFS and all, practically you can do 50,000 but it will slow things down. Google ‘how many files in a folder is too many’ — there are a number of server side processes you’ll be goofing up with that.
Hello @ipstenu ,
If you don’t want to see those files, you can use the Disable File generation from here.
After that, just Regenerate the Assets from here.
This will load the CSS & JS for the page inline in the HTML & there will be 0 files on your site with respect to UAG Assets Generation.
Hope the above solution works for you.
Regards,
Sweta
If you don’t want to see those files, you can use the Disable File generation from here.
And that’s what we told the customer to do. They’re not please to find out they can’t automatically do it because your plugin doesn’t have the ability to natively handle larger sites.
I am aware that sounds harsh. It is. You’ve hit a problem other apps (MediaWiki comes to mind, also other cache apps like WP Rocket, WP Super Cache, etc etc) have also had and solved, by simply _not_ putting all the files in one folder.
