WiredTiger currently has a lock that is used to protect access to the connection wide (globally shared) dhandle list. That lock is currently a spinlock, since operations that hold it are generally short lived. The assumption about short-lived lockers doesn't hold entirely true when the number of open dhandles grows very large.
It would be beneficial to switch the lock from a spinlock to a read/write lock, since most code paths only need to protect against the list changing while they are accessing it.
- is depended on by
-
SERVER-27700 WT secondary performance drops to near-zero with cache full
- Closed
- is duplicated by
-
SERVER-28172 Renaming collection causes permanent performance issue on secondary
- Closed
- is related to
-
WT-3345 Improve rwlock scaling
- Closed