Don’t use on Large Sites!
-
Using this on Large Sites will fill up your entire drive with temporary Min JS and CSS files causing over 1<->20 GB of files created. This is ontop of any other caches you may have.
This also hints at another problem. Due to these CSS files beign served with a unique name, each page load of the users will need a NEW CSS to be downloaded. This will slow down the users that fill more pages.
There was already a ticket open for this, and the only reply was “Strange”.
-
Hi @mgparisi,
First of all, we are sorry about the inconvenience caused. Anyways, we actually needed to investigate why the issue was happening on your website.
However, good news is that, we are preparing a new release within next few days with a bit tweak in our Asset generator mechanism. We have already deployed this on few sites and you won’t be seeing the file size issue anymore with the assets hopefully.
FYI: The file size issue happens in extremely unlikely circumstances hence we said ‘It’s strange’ and needed to investigate a bit more for debugging.
So, if you want, you can contact our support and try out the development version. Or, just wait for the next release & your issue should be resolved.
Anyways, I find this review very harsh to be honest as we always try to help our users. It would be great if you consider changing the rating especially after trying out the dev/upcoming version.
Thank you!
- The topic ‘Don’t use on Large Sites!’ is closed to new replies.
