-
Type: New Feature
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Storage, WiredTiger
-
None
-
(copied to CRM)
When the WT b-tree uses a file per collection or index then it uses a huge number of files for deployments that have a huge number of collections. I want an option to use a file per database for the WT-btree and an LSM tree per database for the WT LSM. For motivation see SERVER-17225
- duplicates
-
SERVER-33220 Understanding number of file descriptors needed by mongod process
- Closed
- is duplicated by
-
SERVER-24384 Extremely slow writes on OSX with WiredTiger and constant collection/index creation+drop
- Closed
-
SERVER-18812 Improve aggregation with $out performance on WiredTiger
- Closed
- is related to
-
SERVER-25025 Improve startup time when there are tens of thousands of collections/indexes on WiredTiger
- Closed
-
SERVER-21067 Investigate having the storage size of a given collection/index/database cached within the WT/KV api
- Closed
- related to
-
SERVER-22642 WiredTiger engine resync stalls with a lot of tables/indexes
- Closed