How to organize my projects to optimize costs
Hi, I'd like to know what would be better to optimize costs in Railway since I'm paying around $40 per month, I don't see that as a lot but well, if I can reduce it, better then.
I have 15 projects. Each one named with the name of the company, and inside it has a Postgres database and a Strapi CMS connected to it.
These receive around 150k requests per month.
2 GB of ram should be enough (I think, lol) to handle that amount of requests (and usage in general), but around 10k requests per month is enough make a single project use 750 MB - 1.25GB of RAM, so I have 15 projects using ~1GB of RAM, which is expensive.
I'd like to ask if it'd be cheaper to create a single project, put there a single Postgres Database (using different schemas for each project), and put the 15 Strapi Admins there, connected to it. Is there any catch-ups for this implementation or something I should know?
If there isn't a clear response to this, and it's something I should try out, let me know! Thanks!
32 Replies
Project ID:
c76a19f8-74a9-4003-8811-1ffb7bf64233what's the average usage of those postgres instances? Strapi is a resource hungry service
Mmm ugh I don't know, how can I check it? Do these images respond to it?
is that from the current month?
Yes
get from a past month, there's a selector on the top of the page
dont forget the egress costs 👀
Ok let me send everything
These are the same two of the last month
in my exprience, 1 shared DB instance for multiple CMS instances should work perfectly fine
but it might become a bottle neck at some point (if it uses more RAM/CPU than your railway plan)
it doesnt show the postgres usage :/
but ok, my point is that the postgres usage is so little (about 50mb~100mb) that it might not be worth it doing all of that work
Sorry wait
Is it ok?
yep, as I guessed
you would save about 7.5$ by doing all of that