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
Version: 10.10.0
Platform: Darwin 17.7.0 xnu-4570.71.2~1
Docker: node:10-slim
In the environment in which we run Node.js, is about 5,000 env variables. With such a large value of variables, it takes much longer to read them. The problem is that Node.js does not cache the result of getenv method call. As a result, the performance of the application falls critically.
That's how the bottom of the flame graph looks like:
Half of the execution time is spent reading env-variables.
The text was updated successfully, but these errors were encountered:
Version: 10.10.0
Platform: Darwin 17.7.0 xnu-4570.71.2~1
Docker: node:10-slim
In the environment in which we run Node.js, is about 5,000 env variables. With such a large value of variables, it takes much longer to read them. The problem is that Node.js does not cache the result of getenv method call. As a result, the performance of the application falls critically.
That's how the bottom of the flame graph looks like:
Half of the execution time is spent reading env-variables.
The text was updated successfully, but these errors were encountered: