Redis adapter ^6.1.1 #492
Comments
|
Hi! Actually it was implemented like that in previous releases, please see the rationale here: #102 |
darrachequesne
added a commit
that referenced
this issue
May 2, 2023
The subscriptionMode option allows to configure how many Redis Pub/Sub channels are used: - "static": 2 channels per namespace Useful when used with dynamic namespaces. - "dynamic": (2 + 1 per public room) channels per namespace The default value, useful when some rooms have a low number of clients (so only a few Socket.IO servers are notified). Related: - #491 - #492 - #493
|
The See: d3388bf Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi There! Recently I'm playing around with upgrading redis adapter and socket IO version an I'm trying to understand one change.
In newer versions we're subscribing to all rooms:
this.subClient.psubscribe(this.channel + "*", onError);For projects handling hundreds thousands of WS connections with multiple machines and node processes this solution is a little bit inefficient. So I decided to rewrite adapter as it worked a couple of versions before, to subscribe and unsubscribe to rooms that I want to. But maybe somehow I'm using socket.io in wrong way. Can you please explain that change? Below in the URL there is my implementation for adapter to subscribe and unsubscribe for rooms that I need at the moment.
Thanks in advance.
https://pastebin.com/8Gr5hKWw
The text was updated successfully, but these errors were encountered: