The developer_memory setting currently changes only memory config within leveldb. It could (and should) lower the worker pool thread count in eleveldb if seen during NIF start up. Currently the thread pool defaults to 71 (a prime number). Recommend lowering it to 5 (another prime number) upon detect of the flag ... if an only if the thread_count setting is not also present.
The developer_memory setting currently changes only memory config within leveldb. It could (and should) lower the worker pool thread count in eleveldb if seen during NIF start up. Currently the thread pool defaults to 71 (a prime number). Recommend lowering it to 5 (another prime number) upon detect of the flag ... if an only if the thread_count setting is not also present.