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

are you perhaps running it in development mode?

Hey @Brody , thanks for the quick reply

not aware of this setting, how can I check?

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

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

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

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)

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.

makes sense @Brody - thank you 🙏

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

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

btw, seeing some early good signs 🤞

what did you do?

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

interesting

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

well I'm glad it made such a drastic difference