MongoDB uses RAM and not Disk for cost calculation?
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?
5 Replies
Project ID:
964949b4-6290-4a34-9986-8e64a5b0c6b2964949b4-6290-4a34-9986-8e64a5b0c6b2
I have changed the start command with:
docker-entrypoint.sh mongod --ipv6 --bind_ip ::,0.0.0.0 --wiredTigerCacheSizeGB 1
and It drastically reduced the RAM consumptionnope, you're now billed by RAM, CPU, DISK and Network Egress.
and sure you can turn on app sleeping, just make sure that it wouldn't affect your application
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