Open hoeken opened 12 months ago
Sorry for the delay. I have seen this behavior also for non-websocket tests, not sure what is causing the memory leak?
Hi again! After some investigation, there is a definite memory leak for websockets. Support was added by another developer but the package has evolved a lot and I'm afraid it is not up to par at the moment. I don't have the knowledge or the time to fix it; if you want to work on it you are most definitely welcome!
I might give it a look at some point. Its definitely meeting my needs for now right now though with wss support working.
I'm using loadtest to test the performance of my websocket server on an embedded device (which is why the #s are so low)
I have a script that tests at different levels of concurrent users, from 1 to 20. Everything works great from 1 to 7, but as soon as I test with a concurrency of 8 the program doesn't exit. It seems this is true for any concurrency # above 7. I am setting --cores to 1 since I want to control exactly how many connections I have to the device.
If I remove the --cores 1 option, then it works fine, although then I have to do some math to get the exact # of connections.
The weird thing is that the script completes and prints statistics, but then it simply doesn't exit as if its waiting for something else to complete.
Also, every time it starts up, it lists a bunch of potential memory leak errors which you can see below:
I am running on Mac with this software installed: