Skip to content
Ate 27 Cents in one day - Discussion

2 years ago

Not a complaint or a problem, just a discussion.

If we take a look in the image here, I'm being charged for 728GB minutely GB of RAM? What does this mean? What is this a measure of? Why is this number so incredibly high? As well as CPU usage? My graphs don't look drastic whatsoever...

Solved

109 Replies

2 years ago

322ea2ee-d764-421d-9d11-77dde0980f62


2 years ago

This is what the observability page looks like for today

1365143986574200852


2 years ago

322ea2ee-d764-421d-9d11-77dde0980f62


2 years ago

It looks like mongodb is taking a giant chunk of this?

1365145518946127873


2 years ago

RAM is probably the most expensive_ish_ resource on Railway (and most platforms), your application seems to use quite a bit -between 500mb and 1gb (specially mongo)- which is billed by the minute.


2 years ago

My stupid dependencies... is Mongo not one of your most popular databases? Is this really just hope much it uses?


2 years ago

Yeah, mongo is pretty popular


2 years ago

So nobody can sustain a mongo database under the $5 plan, lol?


2 years ago

Prob PostgreSQL, MySQL and Mongo


2 years ago

Seems to be using 250 and rising, consistently

1365146582005190696


2 years ago

You can enable serverless to scale it down to zero and then scale back up based on traffic


2 years ago

But yeah, mongo is know for being very mem intensive, together with mysql


2 years ago

I don't really see that being feasable with the amount of time a coldstart would take


2 years ago

Feels weird that nobody can host a very popular database on one of the two plans, especially because it's like, the entire point of this system


2 years ago

I always recommend postgresql if the user wants lower costs


2 years ago

Too late for that 😂


2 years ago

I mean, that's mongodbs fault


2 years ago

I suppose ¯_(ツ)_/¯


2 years ago

250mb is a lot


2 years ago

MongoDB took ~20 cents in one day, * 30 meaning it would be $6 for just one database


2 years ago

@Loudbook this is what i mean (from <#727689277219012669>)

1365277799258001428


2 years ago

7 cents of ram and 11 cents of cpu


2 years ago

thats from your screnshot


2 years ago

oh I am fairly blind aren’t I


2 years ago

do you run it in a metal region by any chance? when i moved mine to metal the cpu costs went wayyy down


2 years ago

here's the latest today

1365278246123343912


2 years ago

i'll check


2 years ago

I am not


2 years ago

I’m going to migrate to a closer data center that’s also on metal


2 years ago

yeah definitely give that a try


2 years ago

mongo seems to run better on metal cpus


2 years ago

Is all of this amd64?


2 years ago

yep


2 years ago

Why not arm?


2 years ago

That would be dirt cheap


2 years ago

idk ask railway


2 years ago

lol


2 years ago

🚂


2 years ago

but anyway you can see here on your observability graph, thats an insane amount of cpu for a small db

1365279040226852986


2 years ago

mine did nonsense like this too before i switched it to metal, i couldnt tell you why it behaved that way but metal cpu good


2 years ago

it now uses so little cpu it barely even registers on the graphs

1365279377411014707


2 years ago

damn


2 years ago

I’m using 0 now


2 years ago

and a fraction of the RAM too


2 years ago

the memory will creep back up as its used


2 years ago

nvm still most of the RAM as before


2 years ago

yeah


2 years ago

i added --wiredTigerEngineConfigString="cache_size=50M" to mine which stopped it from going above 300 randomly, but it still hovers around 300 and theres not really anything you can do about that


rdb

2 years ago

You can use a free Mongo cluster if you don't host it in railway


2 years ago

Well yeah, but I don't want every environment connecting to the same one


rdb

2 years ago

As long as you store less than 500mb iirc


2 years ago

i switched to using one on railway when mongo killed my free cluster randomly 🥲



2 years ago

had a good run tho, that cluster was alive for years


2 years ago

thats strange


2 years ago

nevermind we vibin

1365280782423167046


2 years ago

is your app using the db a lot?


2 years ago

bipolar db


2 years ago

nope


rdb

2 years ago

Always use a Mongo dump every time life feels like it's going a bit too smoothly


2 years ago

yeah!


2 years ago

i regularly do that now


rdb

2 years ago

Railway Pro plan gives you auto backups


rdb

2 years ago

It's p fire


2 years ago

railway pro is also


2 years ago

$20/m


rdb

2 years ago


2 years ago

i'll keep that in mind if my usage ever grows to $20 naturally


2 years ago

but i'm not paying just for the features


2 years ago

i fear


rdb

2 years ago

That's down from 110 last month


2 years ago

what are you hosting


rdb

2 years ago

Few bots and a site


2 years ago

do you not get constant random hangs, errors, and invulnerable volumes


rdb

2 years ago

No


rdb

2 years ago

0 issues


2 years ago

and that costs you $110/m?


rdb

2 years ago

24/7 uptime too


rdb

2 years ago

No there was a specific bot that was 60 alone that I no longer host


2 years ago

what the heck


2 years ago

that's a ton of money


rdb

2 years ago

Big bot in a big server


rdb

2 years ago

Lots and lots of resources


2 years ago

you could get a full VPS with a decent CPU for $50/m


2 years ago

and host all of that


rdb

2 years ago

Too much effort railway ux is better


rdb

2 years ago

Railway makes life so easy that it's worth paying the premium


rdb

2 years ago

But my bots cost a lot because they are high usage


rdb

2 years ago

And also maybe not the most efficient


rdb

2 years ago

💀💀


2 years ago

meanwhile I can't even deploy a template

1365281873529667644


2 years ago

due to


2 years ago

"unknown error"


rdb

2 years ago

What template are you trying to deploy


rdb

2 years ago

I always deploy from GitHub


2 years ago

tailscale subnet router


2 years ago

why 😭


2 years ago

:(


2 years ago

idk why they sobbed but looking at my bio may give a hint of why i sobbed


2 years ago

unknown error is weird tho


2 years ago

but maybe worth a separate thread if it persists


2 years ago

deployed that template now and it seems fine for me


maddsua

2 years ago

Real


2 years ago

you've likely hit the service count limit on the trial plan


2 years ago

Ah well


2 years ago

If I can get my mongodb usage down I’ll consider buying hobby


2 years ago

as a few people have said, that's unfortunately just the reality, mongo uses a lot of memory in comparison to Postgres


2 years ago

Yep I'm not upset


2 years ago

!s


Status changed to Solved brody • over 1 year ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...