Hi,
I created a database in both - Atlas and local deployment - and I see the same amount of bytes used for my database in both. The number is 1.18M. The actual data when extracted in JSON format containing all the collections with their fields is actually using only 80K. So I am wondering what is that extra megabyte of data that is stored in DB?
Locally I am not concerned but since I am using free tier Atlas and it has only 500M available space - how soon will it be filled up to the max if the ratio of used space to actual data size is more than 1 (in my current case 1.18 / 0.080 ~= 14)
Thanks
I’m sure that someone with in-depth knowledge can wade in but the database will not just be storing the data but an amount of other data about the database, collections, indexes and a lot of other information so there will be an overhead to start with.
If you want to check in more detail I’d suggest putting more and more data in and then exporting it and comparing each to see what the overhead is.
I suspect it’ll be a certain amount of storage to start with and then as you insert more data the storage usage will grow according to the actual data size as opposed to growing based on the difference you’ve seen.
Bear in mind the server will also support compression (not sure if the 500MB limit includes compression or raw data size…)
So you’d end up with something like this:
1 Row: 1.1MB
1000 Row: 1.2MB
2000 Row: 1.3MB
3000 Row: 1.4MB
etc, so there is a basic overhead but after that the storage size grows as expected.
I’m away from my home setup at the moment so cannot test but give it a whirl and see what numbers pop out.