16 days ago
I got this alert on my dashboard, sayng hat im reaching limits to my application.
I want to know the following info:
- Why is the price so high? My application has super low traffic, i don't think it would pass the default $5 biling
- Why is it reaching the limit already? we are at the day 6 of the month, i have alredy payed the last month bill, how is this calculated?
- Do you have any tips to make it cheaper?
Attachments
Pinned Solution
16 days ago
Hey, just so that you know, lowering the RAM and CPU limits may result in your affected services crashing due to OOM, which may not be desired. As mentioned above, the best way for you to save on usage is to enable serverless, meaning that your services will only run when necessarily.
Alternatively, you may use a different database that is more memory friendly, such as MariaDB, which should is essentially a drop in replacement for MySQL, or perhaps use something different entirely, such as Postgres.
I would advice you to try a different browser, such as Firefox, if you want to lower the RAM/CPU limit and there is no save/apply button on your end.
6 Replies
16 days ago
Your current billing period usage is $7.68, with memory being the dominant cost at $7.54. The biggest contributor is your Melfy-API service at $4.07 (almost entirely memory), followed by MySQL at $2.93 (also memory). Your Hobby plan includes $5 of resource usage per month, so you're currently looking at about $2.68 in overage. Services consume resources continuously while running, regardless of traffic volume, so even with low traffic your services are using memory 24/7. You can view a per-service breakdown at the Usage page. To reduce costs, you could enable App Sleeping on services that don't need to run constantly, which automatically stops them when idle.
Status changed to Awaiting User Response Railway • 16 days ago
16 days ago
Can you tell me why the memory usage is so high for my mysql and melfy-api? this memory is the local memory or RAM used? My main service is Melfy- backend, wich has the lowest usage. It doesnt make sense.
Status changed to Awaiting Railway Response Railway • 16 days ago
16 days ago
Memory on your bill refers to RAM, not disk storage, and it's billed at $10/GB/month. Your Melfy-API is using roughly 400 MB of RAM and MySQL is using roughly 280 MB, while Melfy-BackEnd only uses about 66 MB. MySQL databases allocate memory for their buffer pool and caches regardless of query volume, which is why it costs more than your backend. You can see exact per-service RAM consumption on the Metrics tab in each service's dashboard. To reduce costs, you can enable Serverless on services that don't need to run 24/7, which automatically stops them when they receive no traffic for 10 minutes.
Status changed to Awaiting User Response Railway • 16 days ago
16 days ago
I cant manage the ram and cpu limits for my services, they are not saving the values, can you help me?
Status changed to Awaiting Railway Response Railway • 16 days ago
16 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • 16 days ago
stela-sm
I cant manage the ram and cpu limits for my services, they are not saving the values, can you help me?
16 days ago
Hey, just so that you know, lowering the RAM and CPU limits may result in your affected services crashing due to OOM, which may not be desired. As mentioned above, the best way for you to save on usage is to enable serverless, meaning that your services will only run when necessarily.
Alternatively, you may use a different database that is more memory friendly, such as MariaDB, which should is essentially a drop in replacement for MySQL, or perhaps use something different entirely, such as Postgres.
I would advice you to try a different browser, such as Firefox, if you want to lower the RAM/CPU limit and there is no save/apply button on your end.
uxuz
Hey, just so that you know, lowering the RAM and CPU limits may result in your affected services crashing due to OOM, which may not be desired. As mentioned above, the best way for you to save on usage is to enable [serverless](https://docs.railway.com/deployments/serverless), meaning that your services will only run when necessarily. Alternatively, you may use a different database that is more memory friendly, such as MariaDB, which should is essentially a drop in replacement for MySQL, or perhaps use something different entirely, such as Postgres. I would advice you to try a different browser, such as Firefox, if you want to lower the RAM/CPU limit and there is no save/apply button on your end.
16 days ago
thank you so much! ill be trying others browsers, because the save/apply option simply doesn't exist on edge.
My application is veeery simple, i hope it wont get that bad if i lower down the limits. Gonna test it.
Status changed to Solved brody • 16 days ago