SignalR IIS worker process does not released

Question

We have a simple signalr server and client running with the backplane enabled. When I looked in to the IIS worker process I found out in the current requests tab there is always this signalr connect is showing.

When I connect like 100 clients 100 current requests are shown in the woker process view. Shouldn't these be removed after connecting or is this the expected behavior from the signalr?

Why would they be removed? The very purpose of SignalR is to keep the connections alive to do push over HTTP — Kevin Gosse, May 05 '17 at 06:47
So if I connect 1000 clients, 1000 requests will be executing all the time? — Janitha Tennakoon, May 05 '17 at 07:30
We have the same issue here and have a growing number of connections that keeps building over time. If we have 100+ clients ok fine we expect to see 100+ threads - but these only increase over time so not sure why they stay open for such long periods of time. — Jeffrey Holmes, Feb 22 '18 at 08:38

score 4 · Answer 1 · answered May 05 '17 at 20:10

4

The threads will close or get reused by new clients, its basically a thread pool, you shouldn't need to worry about it. The only time you need worry about how many threads are open is if you only have limited cpu resources, and a low open thread limit set.

answered May 05 '17 at 20:10

Kelso Sharp

972
8
12

Please cite a source – The One Oct 08 '21 at 18:45
This might not be relevant now, but all of the singalR documentation at the time and its likely still the same, its the nature of the technology. https://learn.microsoft.com/en-us/aspnet/signalr/overview/getting-started/introduction-to-signalr – Kelso Sharp Oct 18 '21 at 17:50

SignalR IIS worker process does not released

1 Answers1