Skip to content

Deduplicate SignalR group messages across connections #61809

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 task done
datwelk opened this issue May 6, 2025 · 0 comments · May be fixed by #61810
Open
1 task done

Deduplicate SignalR group messages across connections #61809

datwelk opened this issue May 6, 2025 · 0 comments · May be fixed by #61810
Labels
area-signalr Includes: SignalR clients and servers

Comments

@datwelk
Copy link

datwelk commented May 6, 2025

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

When a SignalR connection is part of multiple groups, the connection will receive a message destined for the N-groups the connection is a part of also N-times. This leads to unnecessary overhead on the server, the network connection, and the client processing the messages.

Describe the solution you'd like

A common solution for this problem is to deduplicate on the client. This however does not take away the unnecessary network traffic, and requires client side processing.

Both DefaultHubLifetimeManager and RedisHubLifetimeManager know which connections belong to a group. Hence filtering can be done easily server side.

Additional context

No response

@ghost ghost added the area-signalr Includes: SignalR clients and servers label May 6, 2025
@datwelk datwelk linked a pull request May 6, 2025 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-signalr Includes: SignalR clients and servers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant