My bug that never never solved. my app has transaction over websocket like 2000 request per sec.
The bug was memory leak, I use socket.io debugging it was so painfull because I cant fake those request on my local machine.
First time I was blaming socket.io because of memory leak, so I created an app again that mimic the same data transaction over websockets. Turns out I cant reproduce the memory leaks issue with socket.io.
For now on I just load balancing the server. But I'm afraid when the transaction goes bigger and bigger maybe I just throw another load balancing server...
Memory leaks issue are the hardest bug I ever encounter
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
My bug that never never solved. my app has transaction over websocket like 2000 request per sec.
The bug was memory leak, I use
socket.io
debugging it was so painfull because I cant fake those request on my local machine.First time I was blaming
socket.io
because of memory leak, so I created an app again that mimic the same data transaction over websockets. Turns out I cant reproduce the memory leaks issue with socket.io.For now on I just load balancing the server. But I'm afraid when the transaction goes bigger and bigger maybe I just throw another load balancing server...
Memory leaks issue are the hardest bug I ever encounter