The JADE 2022 release meets tomorrow’s business demands.
Currently strings are discarded from the string pool very aggressively when the pool size exceeds the limit. This is probably not appropriate any more, with 64-bit address space and more memory available. If the limit is set too low, it can have a substantial impact on performance.
A user can accidently set the limit way too low, for example by specifying StringPoolLimit=12 instead of StringPoolLimit=12M. This would invoke the default of 64K.
This could be automatically improved the same way methods were done for JADE 2018 - ie ensuring a string isn't discarded for some period of time after it was created - defaulting to 10 minutes, and overridable in the ini file.
John Porter
