Hacker News Reader

> 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.

View on HN

Server Side Blazor will have to store the current Virtual DOM Representation in memory for each client, so that it can do diffing on it if a request comes in for that client and return the diffs.

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?

Reply on news.ycombinator.com