5 months ago
I'm a newbie, as if it isn't obvious from this question. I deployed LinkDing, a very small bookmark app. I had the service running 24/7 at max Hobby resources before realizing I could reduce it.
I've since change the resources from 8 vcpu and 8 gigs ram to .5 vcpu and .5 gigs of ram, but the estimated cost is relatively the same.
3 Replies
5 months ago
hey, youre charged for what your service winds up using, not for what's available. if you had 8 vCPU and memory, your service just had more headroom to utilize additional cpu/memory if needed. if youre concerned about limits/over-charging, you can set a usage limit that will automatically stop all services https://docs.railway.com/reference/usage-limits
5 months ago
Thank you. I assumed having 8 vCPUs and 8 gigs, even if unused but available, would cost more, as it is tying the resources up; therefore, having minimum resources tied up will be less. I've set usage limits, but at the end of the day I don't think Railway is going to be economical for me. Bummer.
Edit: grammar
haltncatchfire
Thank you. I assumed having 8 vCPUs and 8 gigs, even if unused but available, would cost more, as it is tying the resources up; therefore, having minimum resources tied up will be less. I've set usage limits, but at the end of the day I don't think Railway is going to be economical for me. Bummer. Edit: grammar
5 months ago
perhaps the most you can try to do is enable serverless https://docs.railway.com/reference/app-sleeping which puts the app to sleep if its unused, but keep in mind that any activity (i.e frequent pings or outside packets) will not allow the app to sleep. allowing the app to sleep can save in terms of costs