Skip to content

Timeout error from silo when number of connections goes beyond 10k #7961

Open

Description

Hi Team, we are having following services:

  1. Microsoft SingalR Hub service.
  2. Orleans as a backplane for SignalR (created the Silo host and registered signalR hub as silo client)

We have deployed these apps on EKS and have assigned 6 Core CPU and 6G memory to Silo Pod, hub has been provisioned moderately with 2core CPU and 2GB memory, we are trying performance tests and trying to figure out the optimum load single silo can handle.

With this setup in place, we are facing time-out errors from the Silo side while making the ClientGrain connections, when our singalR connection count goes beyond 10k, We observed the latency on Silo dashboard it gets increased very massively after a certain number of connections.

Can you guys help me to come up with the optimum number of connections a single silo should support and optimum resources like memory and CPU we should assign to Silo pod.

Note: I have used two silo hosts to share the load with LOAD_SHEDDING_LIMIT set to 30.

Your help will be highly appreciated as we are kind of stuck till 10k connections currently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions