Excessive memory usage and $$ to keep Next.js project running | Railway | Page 1

dusty tulip Sep 1, 2024, 4:19 PM

#

I have a Next.js Project with currently 0 active users costing $20 a month just to keep it live. Any suggestions on how to debug and reduce this memory usage? Thanks!

hot ospreyBOT Sep 1, 2024, 4:19 PM

#

Project ID: 14a3af77-b63d-4ec2-97c9-16784e1486e3

dusty tulip Sep 1, 2024, 4:20 PM

#

14a3af77-b63d-4ec2-97c9-16784e1486e3

prime plank Sep 1, 2024, 4:20 PM

#

are you perhaps running it in development mode?

dusty tulip Sep 1, 2024, 4:22 PM

#

Hey @prime plank , thanks for the quick reply

#

not aware of this setting, how can I check?

prime plank Sep 1, 2024, 4:23 PM

#

not a railway setting, you have to know what mode you are running your next site in

dusty tulip Sep 1, 2024, 4:23 PM

#

i mean, i don't have any different build/start command, so I'm using the default

prime plank Sep 1, 2024, 4:25 PM

#

are you following next's best practices when running in a production environment

dusty tulip Sep 1, 2024, 4:40 PM

#

yeah, and i'm running on production mode... i've got rid of next/image + updated next.js to the latest stable (14.2) and will push live to see if I see any improvements (also added the flag --experimental-debug-memory-usage)

prime plank Sep 1, 2024, 4:45 PM

#

then I'm not too sure what else I can help with, it seems like you covered everything I would have said already.

the only thing left I can say is that you should ask the next community for support, as railway doesn't have any more observability in what your code is doing than you would, we are simply running your app and reporting on the metrics it uses.

dusty tulip Sep 1, 2024, 4:46 PM

#

makes sense @prime plank - thank you 🙏

prime plank Sep 1, 2024, 4:47 PM

#

sorry we couldn't be of more help but unfortunately we aren't able to offer application level support here beyond some basic pointers.

dusty tulip Sep 1, 2024, 4:52 PM

#

you're always very helpful, super grateful for all the support - this is not the first time you help me out salute_guy

#

btw, seeing some early good signs 🤞

prime plank Sep 1, 2024, 4:53 PM

#

what did you do?

dusty tulip Sep 1, 2024, 4:54 PM

#

got rid of next/image + updated next.js to the latest stable (14.2)

#

i think should be mostly a memory problem from the version i was using

prime plank Sep 1, 2024, 4:54 PM

#

interesting

dusty tulip Sep 1, 2024, 4:55 PM

#

next/image is barely used on my app, but i've seen some reports of problems with it so i did both changes

#

i was on next 13.1.1

prime plank Sep 1, 2024, 4:57 PM

#

well I'm glad it made such a drastic difference

#Excessive memory usage and $$ to keep Next.js project running