Closed reyemtm closed 8 months ago
I think I figured it out.
Do you mind sharing how you figured it out? I'm facing the same issue.
You need to make sure you are not constantly opening a new pool but instead actually using the same pool for each call, instantiated at a higher level, if that makes sense.
In NodeJS, the pool seems to keep spawning workers and not closing them, or not closing them soon enough, leading to a 1.5G memory usage without to use the max memory available. Is there a way to check and see if the pool is active and if so destroy it?