Lot of "ignoring unknown request" in Debug about socket.io-redis-adapter HOT 5 CLOSED

Awesome, thanks for the update 👍

I've added a note about the publishOnSpecificResponseChannel option here: https://socket.io/docs/v4/redis-adapter/#default-adapter

from socket.io-redis-adapter.

Hi! You can set publishOnSpecificResponseChannel to true, in that case the Socket.IO servers will use a Redis channel specific to the requesting node to respond (and not publish to all nodes).

from socket.io-redis-adapter.

Source:

When publishOnSpecificResponseChannel is set to false (default value), the response is sent to all nodes, but only one node is interested by the response (channel name: this.responseChannel).

When publishOnSpecificResponseChannel is set to true, the response is only sent to the requesting node (channel name: ${this.responseChannel}${request.uid}#).

The latter should be the default behavior, as the filtering is done by Redis, but to maintain backward-compatibility the default value is false.

from socket.io-redis-adapter.

Thanks for your quick answer !

In your point of view what are the pros/cons of both options ? We will use socket.io and this adapter on heavy load (+1000req/s) so i'm trying to find the most efficient (and safest) way to do this.

from socket.io-redis-adapter.

Thanks for your complete answer. We improved performances by a lot.

I'll share some benchmark result between the two options.
20Vcpu, 30Ghz allocated CPU, 32Go RAM

With publishOnSpecificResponseChannel to 'false' it takes 24Ghz on average and with it to 'true' it takes 19Ghz on average, so we have an improvement of 21%.

This tests are made with Vsphere metrics reporter and are not very precise so take it with caution.

Thanks again, I close this issue.

from socket.io-redis-adapter.