SERVER-25025 targets inefficiencies in startup initialization in MongoDB's use of WiredTiger.
Even with these optimizations, given a large number of collections, we could still benefit from parallelizing the startup procedure. It is currently single-threaded and mostly CPU-bound, spending almost all CPU time-per-collection in setTableLogging(). This uses an expensive "metadata:create" cursor to determine whether or not a table is logged.
- is related to
-
SERVER-54074 [v4.0] Log start and end of changes to table log settings
- Closed
-
SERVER-55479 Invariant that the first table checked in WiredTigerUtil::setTableLogging() is the _mdb_catalog
- Closed
-
WT-5394 fast way to fetch logging config for a table
- Closed
- related to
-
SERVER-25025 Improve startup time when there are tens of thousands of collections/indexes on WiredTiger
- Closed