You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using this with a web api server (single logger for the application)... when running under load tests (few thousand concurrent users and millions of requests) the RAM usage will grow to several GB. Without this module, it stays under 50mb.
I noticed the underlying elastic node library is deprecated in favor of a new official library, and that may resolve the issue... Also, may want to replace the moment use with specific date-fns module.
I won't be able to re-create or re-test as we've removed this module from our services and relying on output log shipping from the stdout/stderror logs now. Just wanted to report the issue upstream.
The text was updated successfully, but these errors were encountered:
Using this with a web api server (single logger for the application)... when running under load tests (few thousand concurrent users and millions of requests) the RAM usage will grow to several GB. Without this module, it stays under 50mb.
I noticed the underlying elastic node library is deprecated in favor of a new official library, and that may resolve the issue... Also, may want to replace the moment use with specific date-fns module.
I won't be able to re-create or re-test as we've removed this module from our services and relying on output log shipping from the stdout/stderror logs now. Just wanted to report the issue upstream.
The text was updated successfully, but these errors were encountered: