Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Test concurrent connection limit on different Azure VM sizes #5311

Closed
8 tasks
BrennanConroy opened this issue Jun 27, 2018 · 3 comments
Closed
8 tasks

Test concurrent connection limit on different Azure VM sizes #5311

BrennanConroy opened this issue Jun 27, 2018 · 3 comments
Assignees
@BrennanConroy
Labels
area-signalr Includes: SignalR clients and servers task
Milestone
3.0.0

Comments

@BrennanConroy
Copy link
Member

Collect connection count, CPU %, Memory Usage
Machine Sizes:

  • B1s (4,900 connections, 1GB RAM limiting factor, CPU ~10%) Specs: 1GB RAM, 1 CPU
  • B2s (82,000 connections, CPU and RAM basically 100%) Specs: 4 GB RAM, 2 CPU
  • D2s_v3 (110,000 connections, CPU 100%, RAM 80%) Specs: 8 GB RAM, 2 CPU
  • D4s_v3 (160,000 connections, CPU 100%, RAM 50%, connections started disconnecting) Specs: 16 GB RAM, 4 CPU
  • D8s_v3 Specs: 32 GB RAM, 8 CPU
  • D16s_v3 Specs: 64 GB RAM, 16 CPU
  • D32s_v3 Specs: 128 GB RAM, 32 CPU
  • D64s_v3 Specs: 256 GB RAM, 64 CPU

Note: Test Linux vs. Windows VMs to see if there is a difference
@BrennanConroy BrennanConroy self-assigned this Jul 11, 2018
@NickCraver
Copy link
Member

We're interested in the results here ;)

@blahblehblah
Copy link

blahblehblah commented Nov 25, 2018 •
edited

VERY interested!

@aspnet-hello aspnet-hello transferred this issue from aspnet/SignalR Dec 17, 2018
@aspnet-hello aspnet-hello added this to the 3.0.0 milestone Dec 17, 2018
@aspnet-hello aspnet-hello added area-signalr Includes: SignalR clients and servers cost: M labels Dec 17, 2018
@BrennanConroy BrennanConroy mentioned this issue Jan 24, 2019
Closed
@analogrelay
Copy link
Contributor

Closing this since performance is a constant concern and workstream for us, but the specifics of this issue aren't really relevant any more. The concern is that this data would be based on our specific conditions and would get stale really fast.

@analogrelay analogrelay mentioned this issue Apr 4, 2019
Merged
@dotnet dotnet locked as resolved and limited conversation to collaborators Dec 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@BrennanConroy BrennanConroy

Labels
area-signalr Includes: SignalR clients and servers task
Projects
None yet
Milestone
3.0.0
Development

No branches or pull requests
5 participants
@analogrelay @NickCraver @BrennanConroy @blahblehblah @aspnet-hello