4 ms·
Server Side Blazor performance should be similar to Server Side generated web pages, except the framework allows for SPA-style interactions instead of full page
by caleblloyd 8y ago
Server Side Blazor performance should be similar to Server Side generated web pages, except the framework allows for SPA-style interactions instead of full page reloads.
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.
With the rise of serverless and edge computing (think cloudflare workers), I wouldn't be surprised if patterns emerge to running this at the edge.
I agree I wouldn't put any high traffic apps on Server Side Blazor from the get-go. But for Enterprise apps with high complexity and a small user base, I think it would greatly streamline development.
- shadowmint 8y 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.
- caleblloyd 8y agoServer 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?