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 slsk-client over time creates huge increase in CPU and RAM usage 🔥. It got so bad that leaving my application running over night which is using this module had 100% CPU usage on one core and it would not come down. Thank god it was only using one core 😅
Took my time to debug this and found that peerSearchRequests array was collecting a lot of information. There seemed to be no other use for this array collection other then debugging (please correct me here). As a test i removed that part and issues CPU and RAM increase dropped drastically.
Here's a comparison where I'm only monitoring resource usage of a small application using slsk-client:
I'm creating a pull request in a moment and linking this issue with it.
In case this does not get merged anytime soon, feel free to use my fork (master branch) https://github.com/sortofdev/slsk-client which has a fix for this applied.
The text was updated successfully, but these errors were encountered:
Using slsk-client over time creates huge increase in CPU and RAM usage 🔥. It got so bad that leaving my application running over night which is using this module had 100% CPU usage on one core and it would not come down. Thank god it was only using one core 😅
Took my time to debug this and found that peerSearchRequests array was collecting a lot of information. There seemed to be no other use for this array collection other then debugging (please correct me here). As a test i removed that part and issues CPU and RAM increase dropped drastically.
Here's a comparison where I'm only monitoring resource usage of a small application using slsk-client:
I'm creating a pull request in a moment and linking this issue with it.
In case this does not get merged anytime soon, feel free to use my fork (master branch) https://github.com/sortofdev/slsk-client which has a fix for this applied.
The text was updated successfully, but these errors were encountered: