News for hackers. Stuff that matters.

A comment on The Performance Cost of Server Side Rendered React on Node.js. Parent comment

Re:The Performance Cost of Server Side Rendered React on Nod... by nathan_long on Monday November 20, 2017 @02:50PM (#15742653)
Sure, but every user has to do that initial page load. If all initial page loads are slow and expensive, it affects the user experience and costs money.

Also, if you start getting requests faster than you can do the initial render, each subsequent user has to wait in line longer than the one before. Your server-side framework won't even show you how long people waited for a TCP connection.

[ Parent | on HN ]
Re:The Performance Cost of Server Side Rendered React on Nod... by scyber on Monday November 20, 2017 @04:59PM (#15743696)
If the Server rendered page is not user specific and is generic for all users then it can be cached and served quickly. Then only potentially one user would experience a slowdown and you can serve much faster.

Of course then you get into the fun of cache management and invalidation.

[ Parent | on HN ]
Re:The Performance Cost of Server Side Rendered React on Nod... by nathan_long on Wednesday November 22, 2017 @09:18AM (#15756919)
Elixir Phoenix has a game-changing approach here because of how it compiles templates. Effectively, the static part is always cached (until the template changes), but the dynamic part is never cached. Nothing to manage.

See http://nathanmlong.com/2016/11/elixir-and-io-lists-part-2-io... for explanation.

[ Parent | on HN ]
Re:The Performance Cost of Server Side Rendered React on Nod... by kraftman on Monday November 20, 2017 @03:06PM (#15742775)
But they're going to have to wait for the initial page load either way, whether it's rendered server side and sent over or they're shown some static content until its rendered client side?
[ Parent | on HN ]
Re:The Performance Cost of Server Side Rendered React on Nod... by pmontra on Monday November 20, 2017 @03:08PM (#15742784)
They do, but the load will be spread among clients. The issue here is the load on the server.
[ Parent | on HN ]
Re:The Performance Cost of Server Side Rendered React on Nod... by kraftman on Monday November 20, 2017 @03:24PM (#15742900)
I guess it depends on which direction you're coming from. From a traditional server side point of view, you're reducing the server work to just that first page load and making the client do the rest.
[ Parent | on HN ]
Re:The Performance Cost of Server Side Rendered React on Nod... by nathan_long on Monday November 20, 2017 @04:24PM (#15743426)
True. But making all server-side renders really efficient and fast is an option, too. http://nathanmlong.com/2016/11/elixir-and-io-lists-part-2-io...
[ Parent | on HN ]