Efficient way to access SignalR Hub Context in API controllers

Question

Couple of my API controllers need to have access to Hub Context and I know that the GlobalHost.ConnectionManager.GetHubContext call is expensive. Is there an efficient way to do that?

halter73 · Accepted Answer · 2015-01-09 19:58:49Z

3

How do you know the GlobalHost.ConnectionManager.GetHubContext call is expensive?

I just tried calling GetHubContext 10,000 times in a loop and that took 174 milliseconds on my machine. That means each call averaged 0.0000174 seconds. I don't think that is particularly expensive in the context of most Web API calls or web request in general.

If the very first call to GetHubContext is made before any SignalR connections are established, then that the initial call will take longer. On my machine, this first call took 96 milliseconds. This time was spent initializing some SignalR singletons that would normally be initialized when the first SignalR connection is established. Subsequent calls averaged the .0174 milliseconds referenced above.

If that's too expensive, you can always store the returned IHubContext in a singleton. It's thread-safe.

edited Jan 9, 2015 at 19:58

answered Jan 8, 2015 at 20:00

halter73

15.3k3 gold badges52 silver badges65 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Efficient way to access SignalR Hub Context in API controllers

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related