Limit .next folder size in production environments #43177
abriginets
started this conversation in
Ideas
Replies: 1 comment
-
I don't know why this was converted from issue to a discussion but this is something that was breaking my production build for months and I still got no response from Next.JS team. At least let me know if i should wait for any improvements or try to find a workaround myself. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the feature you'd like to request
Hello. I'm hosting my NextJS instance on Render (https://render.com/) and I mentioned that my site is crashing from time to time. After spending sime time investigating and contacting Render support it appears that Render allocates 15GB of disk space to each instance of project deployment which NextJS can eat up really fast. At this moment
.next
folder gained 8GB for the last 5 days. I could purchase additional disk space but then my deployment won't be able to support scaling which is not something I am ready to accept. It would be great to limit size of page caches and remove the least accessed pages if their overall size approaches the desired limits.Describe the solution you'd like
Implement Redis-like eviction policies: https://redis.io/docs/reference/eviction/
OR
Compress
.html
files with gzip and put them on disk with.gz
extension. cache-manager's node-cache-manager-fs-hash plugin handles it pretty well even under heavy loads.Describe alternatives you've considered
¯\_(ツ)_/¯
Beta Was this translation helpful? Give feedback.
All reactions