22 Replies
Project ID:
fb928ae2-62f0-4f8f-be68-9f7902efbebdfb928ae2-62f0-4f8f-be68-9f7902efbebd
I'd say the limiting factor would be the 512mb of ram on the trial plan
also, not the best idea to use nodemon on railway, can cause instabilitys in a production environment
no i have this plan of 32gb of RAM
oh my bad, discord didnt show a pro badge
what do you want the memory limit for node to be set to?
how can i solve the issue i try to change the response of controller, with less data in getAll controllers
but i have the same result
this question is about increasing the node memory limit, what do you want the memory limit for node to be set to?
you can set 50 mb?
that would cause massive instabilities
this question is about increasing the node memory limit
en el body parser
in the body parser
i think you are getting off track
app.use(bodyParser.json({ limit: '50mb' }));
app.use(bodyParser.urlencoded({ limit: '50mb', extended: true }));
i dont see what this has to do with the original question
my question its about the issue in the raylways console, i ask at chat gpt and it say i should to increase the nodes memory limit
okay what do you want to increase it to??
give me a number
12, 16, 24 gigabytes, what do you want?
if i change this, itll have a extra cost in my actual membership?
i can prove with 12
you pay for the usage, correct
and i check if this solve the issue
set a service variable
NODE_OPTIONS = --max-old-space-size=12288ok thanks, but it cant solve the issue, i need other tread for it?
at this point im pretty sure this is a code issue and not an issue with railway
ok ill recheck the code in local then thank you with same information