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
{{ message }}
This repository was archived by the owner on Nov 9, 2017. It is now read-only.
When running the server and logging the amount of allocated physical memory by the process, the amount of javascript managed memory and CPU usage, I am seeing a steady increase in allocated physical memory while the javascript memory is stable. That seems to indicate a memory leak in native code which should be investigated.
For the test I used the test-example/testSocketIO.js script with 10 clients.
Note that in the graph there is a drop in CPU usage and a stabilization of memory usage, this corresponds to market close.
When running the server and logging the amount of allocated physical memory by the process, the amount of javascript managed memory and CPU usage, I am seeing a steady increase in allocated physical memory while the javascript memory is stable. That seems to indicate a memory leak in native code which should be investigated.
For the test I used the test-example/testSocketIO.js script with 10 clients.
Note that in the graph there is a drop in CPU usage and a stabilization of memory usage, this corresponds to market close.