MongoDB uses RAM and not Disk for cost calculation?

drdraxiPRO

a year ago

I build small stuff and I noticed that Mongo is usually the priciest service for me.
I would've thought that after migration to volumes it would bill disk space in the volume instead of RAM?
I can see that in the volume I have around 450MB used but I got $0 in the disk bill.
Can I turn on sleeping on Mongo? Kinda scared to try. 😬

Is that the intended behaviour or is there something wrong with my project?

0 Replies

drdraxiPRO

a year ago

964949b4-6290-4a34-9986-8e64a5b0c6b2


a year ago

I have changed the start command with:
[docker-entrypoint.sh](docker-entrypoint.sh) mongod --ipv6 --bind_ip ::,0.0.0.0 --wiredTigerCacheSizeGB 1
and It drastically reduced the RAM consumption


a year ago

nope, you're now billed by RAM, CPU, DISK and Network Egress.


a year ago

and sure you can turn on app sleeping, just make sure that it wouldn't affect your application


drdraxiPRO

a year ago

Well yeah but I would think that after migration to the Volume that is mounted at /data/db, the data would live in there and not in RAM.
That's why I'm confused by the $0.0000 in the Disk column for the Mongo service