Due to the data structure of MongoDB, data storage space is much occupied compared with traditional relational databases.
The hard disk space utilization is not negligible for storing infrequently used backup data.
Take MYSQL as an example. Remember to check others' test results on the Internet. For the same data, MongoDB occupies 500 m + and MySQL InnoDB occupies 200 m +, myISAM only occupies more than 40 MB of space.
Of course, the test results have a lot to do with the content of the original data and many other aspects. Such data has no standard indicators and is not reliable, but at least representative.
You may say that there is no difference between several hundred m, but you should not forget that if the difference is massive, the problem becomes obvious. Without petabytes, the difference between several terabytes is also considerable.
So my problem is:Is there any good solution for storing backup data that is not used for a long time?
At present, I think the simplest and most feasible method is to directly compress dump data files, such as GZ, bz2, and even RAR on Windows.
Because there are a large number of duplicate keys in the data, it is generally possible to compress at least half of them. If the log and other data with a higher compression rate, the compression rate will be higher.
............ Good soil solution--| ...... However, it is effective despite the soil. Do you know any better solutions?
---------------------------------------------- I am a split line --------------------------------------------------
Recently I plan to buy some vacuum compression bags to pack all the quilts used in winter. In fact, I am not trying to save space, .................. This plum rain season is too Nima Tide !!! Moldy everywhere !!! # % &(*