While working on SERVER-82688, we discovered that WT statically allocates memory for a session array as part of wiredtiger_open. The default session_max value in server is 33,000 and opening WiredTiger with this value of session_max would mean roughly 924MB allocated. This value greatly scales as the number of sessions increase (this was a point of investigation in SERVER-82688, more info can be found in that ticket).

This sparked a conversation about whether it was worth investigating the way WT allocates this memory and whether it's feasible to do a dynamic allocation later on. Especially so since not all of those 33,000 sessions would be used for WiredTiger.

On the server side, we are looking toward potentially increasing the session_max number to 128,000 to match the maximum number of connections we support per node and potentially avoid any crashes in the future in the event the number of connections exceeds session_max. 

The conclusion of investigation in this ticket will drive our decision.