New answers tagged compression
This online compression is extra cost option. And moreover usually online compression has worse compression ratio, then offline one. It's because the 1st one work on row level while the latter one works on block level. So if you really want to spare some space in the database and your old data are mostly read-only you should use: ALTER TABLE table_name MOVE ...
You can rebuild the indexes after or use the WITH UPDATE INDEX when executing your statement. E.g. ALTER TABLE table_name MOVE COMPRESS FOR ALL OPERATIONS WITH UPDATE INDEX; Note. Your statement will not compress existing data: only future data inserted.
You can see network activity in a replicated and or sharded environment despite not sending any requests to the cluster proactively. I also just came across dirty % in mongostat while testing WT. It appears to be the % of in-memory pages.
Top 50 recent answers are included