Closed leonardo2707 closed 3 years ago
I just found out that this is not the right place to ask these questions, so I'm going to migrate the question to what I believe is the right place and close this issue.
If someone went to this issue page because of the same question, I asked the same question on couchdb's git link of the issue on couchdb
Hello, I've been using couchdb in production for almost 2 years, and in this period I realized how greedy the couchdb is with the hard disk. At this time I've been performing views compression and database compression periodically, but my free space is decreasing (obviously because I'm not deleting any data), but I would like to know if there is a more thorough way to do the compression as per shards, is it possible to do shard compression by shard?
Environment: I'm using couchdb version 2.3.1 on docker, I have 4 database replicas, 3 on industrial NUC's, 1 on amazon server
Example of database compression I'm doing:
Example of view compression I'm doing: