Skip to content

Deduplicate SignalR group messages across connections #61809

Open
@datwelk

Description

@datwelk

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

Activity

ghost added
area-signalrIncludes: SignalR clients and servers
on May 6, 2025
linked a pull request that will close this issue on May 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-signalrIncludes: SignalR clients and servers

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      Participants

      @datwelk

      Issue actions

        Deduplicate SignalR group messages across connections · Issue #61809 · dotnet/aspnetcore