Loading...

XML

Word

Printable

JSON

Type: New Feature
Resolution: Won't Do
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Storage, WiredTiger
Labels:
None

Case:
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

(1 related to)

Assignee:: Brian Lane
Reporter:: Mark Callaghan
Participants:: Asya Kamsky, Benety Goh, Brian Lane, Chad Kreimendahl, Chad Kreimendahl, Daniel Doubrovkine, Dieter Guendisch, Francisco Alejandro Lozano López, Mark Callaghan, Michael, Nathan Thiya, Peter Colclough, Ramon Fernandez Marina, Vipin Garg
Votes:: 37 Vote for this issue
Watchers:: 62 Start watching this issue

Created:: Mar 20 2015 04:21:45 PM UTC
Updated:: Jun 22 2022 06:01:06 PM UTC
Resolved:: Dec 10 2020 02:07:19 AM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates