2 months ago
I was charged $173 this month for salary workers, well actually for memory, but it was related to salary workers. And I can't seem to get the salary worker to allow me to control the amount of RAM it's using. I've been trying to set it in the scale settings, but it doesn't stick. So I could really use some help getting the, I'd like to not allow it to use more than a gig of RAM. And you know, anything else I can do to reduce the amount of usage coming from the salary workers.
7 Replies
2 months ago
Your "storyos Celery" service is the primary cost driver, with $1.22 in memory charges so far this current billing period (your last invoice of $173.48 was mostly $171.81 in memory). You can cap memory per replica by going to your service's Settings > Deploy > Replica Limits and setting a memory limit there (e.g., 1 GB), as described in our cost control docs. Note that if your Celery worker exceeds the limit, it will be OOM-killed and crash, so you may also want to configure Celery's own worker memory limits (e.g., --max-memory-per-child). You can also set a workspace-level usage limit with a hard cap to prevent unexpected charges in future billing cycles.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
When I adjust my replica limits, they just seem to change back to the old one before. I don't want it to go back up.
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Do you need to save replica limits? If so, how do you do that?
2 months 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 Railway • about 2 months ago
drewfiero
Do you need to save replica limits? If so, how do you do that?
2 months ago
After configuring the limits, you must redeploy your services.
2 months ago
The limits don't even stick longer than 1 minute and they don't deploy
2 months ago
The setting resets and doesn't stick on deployment. It always says 32 vCPU and 32 GB Memory
Attachments