[NEXT-1314] High memory usage in deployed Next.js project

Problem

Verify canary release - [X] I verified that the issue exists in the latest Next.js canary release Provide environment information [code block] Which area(s) of Next.js are affected? (leave empty if unsure) _No response_ Link to the code that reproduces this issue https://codesandbox.io/p/github/ProchaLu/next-js-ram-example/ To Reproduce - Clone the repository: https://github.com/ProchaLu/next-js-ram-example - Deploy the project on Fly.io Describe the Bug I have been working on a small project to reproduce an issue related to memory usage in Next.js. The project is built using the Next.js canary version `13.4.3-canary.1`. It utilizes Next.js with App Router and Server Actions and does not use a database. The problem arises when deploying the project on different platforms and observing the memory usage behavior. I have deployed the project on multiple platforms for testing purposes, including Vercel and Fly.io. - On Vercel: https://next-js-ram-example.vercel.app/ When interacting with the deployed version on Vercel, the project responds as expected. The memory usage remains stable and does not show any significant increase or latency - On Fly.io: https://memory-test.fly.dev/ However, when deploying the project on Fly.io, I noticed that the memory usage constantly remains around 220 MB, even during normal usage scenarios Expected Behavior I expect the small project to run smoothly without encountering any memory-related issues when deployed