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
I have created a simple test case to demonstrate that RedisStore is leaking pubsub channels when using xhr-polling on both a single and clustered processes. This uses the following versions.
Node 0.8.14
Socket.IO 0.9.11
The test starts a stripped down Socket.IO server and then another process connects 100 xhr-polling clients at a rate of 1 per second. The server logs Redis Pub/Sub data and the number of connected sockets.
Single Process
The single process uses this server. On a single process here are the results of the test showing leaking Pub/Sub channels.
I have created a patch for this. Here are the results of the test using the patch
Clustered processes
The Clustered process test uses this server. Here is a graph of one of two processes showing leaking Pub/Sub channels and connections.
Results with the patch show connections are removed ok but Pub/Sub channels still leak.
The text was updated successfully, but these errors were encountered:
I have created a simple test case to demonstrate that RedisStore is leaking pubsub channels when using xhr-polling on both a single and clustered processes. This uses the following versions.
The test starts a stripped down Socket.IO server and then another process connects 100 xhr-polling clients at a rate of 1 per second. The server logs Redis Pub/Sub data and the number of connected sockets.
Single Process
The single process uses this server. On a single process here are the results of the test showing leaking Pub/Sub channels.
I have created a patch for this. Here are the results of the test using the patch
Clustered processes
The Clustered process test uses this server. Here is a graph of one of two processes showing leaking Pub/Sub channels and connections.
Results with the patch show connections are removed ok but Pub/Sub channels still leak.
The text was updated successfully, but these errors were encountered: