|
|
|
|
|
by shadowmint
2822 days ago
|
|
> There is added resource utilization from tracking session state on the server, but if done properly it could be as little as 1MB or so per active client connection. Just curious, where did you pull this number out of? I've never seen a SignalR connection use that little memory for anything. |
|
1MB is my estimate for the Virtual DOM and associated independent state for each client. I was not factoring in the SignalR per-connection memory footprint, I imagine that would already be pretty optimized?