Threads

Upgrading @optimizely/optimizely-sdk from v4.10 to v5.0.0 caused massive memory consumption growth in NodeJS services, with otherwise identical config. v5.0.0 instantiates the ODP (Optimizely Data Platform) classes eagerly at createInstance time even when ODP is not used, which accounts for the memory jump.

Fixed in @optimizely/optimizely-sdk 5.0.1. The key change: ODP classes are no longer instantiated when you pass odpOptions: { disabled: true } to createInstance. If you do not use ODP, upgrade to 5.0.1+ and set: createInstance({ datafile, odpOptions: { disabled: true } }). The maintainer confirmed this brings memory usage back in line with v4. A lighter-weight lite bundle (@optimizely/optimizely-sdk/lite, intended for edge) is another option for memory-constrained deployments.

Source: https://github.com/optimizely/javascript-sdk/issues/894

Source: https://github.com/optimizely/javascript-sdk/issues/894