-
Type:
Improvement
-
Resolution: Won't Do
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Currently the spill WT instance is initialized on startup. However this means that even if there are never any queries run that spill to disk, we still have the extra memory overhead of running this additional WT instance. In order to alleviate this, we may want to consider initializing the spill WT instance lazily upon the first query that spills.
- is related to
-
SERVER-108257 Lower WiredTiger max sessions for spill engine
-
- Closed
-