Broken out fork of the ASP.NET Core's SignalR load testing tool 'Crankier' that's able to build and run stand-alone (i.e., without the rest of the ASP.NET Core build environment).
Original tool repository: https://github.com/dotnet/aspnetcore/tree/master/src/SignalR/perf/benchmarkapps/Crankier
The local command launches a set of local worker clients to establish connections to your SignalR server.
> dotnet run -- help local
Usage: local [options]
Options:
--target-url <TARGET_URL> The URL to run the test against.
--workers <WORKER_COUNT> The number of workers to use.
--connections <CONNECTION_COUNT> The number of connections per worker to use.
--send-duration <SEND_DURATION_IN_SECONDS> The send duration to use.
--transport <TRANSPORT> The transport to use (defaults to WebSockets).
--worker-debug Provide this switch to have the worker wait for the debugger.
Notes:
TARGET_URLneeds to be the route to your hub exposed byUseSignalrin your application.CONNECTION_COUNTdefaults to 10,000.SEND_DURATION_IN_SECONDSdefaults to 300WORKER_COUNTdefaults to 1
Attempt to make 10,000 connections to the echo hub using WebSockets and 10 workers:
dotnet run -- local --target-url https://localhost:5001/echo --workers 10
Attempt to make 5,000 connections to the echo hub using Long Polling
dotnet run -- local --target-url https://localhost:5001/echo --connections 5000 --transport LongPolling
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent