3 ms·
I guess I'm the rare oldie that don't agree that the frontend/html was/is better without modern js frameworks / spa apps. Maybe because I built SPAs already pr
by brimstedt 5y ago
I guess I'm the rare oldie that don't agree that the frontend/html was/is better without modern js frameworks / spa apps.
Maybe because I built SPAs already pre -10 and I think that finally (as Vue entered the scene) even frontend development can be fun, structured, testable, etc.
But the reason I write is this:
When it comes to SSR, I still think node/js is absurdely slow.
Compared to almost any java rendering backends, where I'd expect no more than 50ms response time/thread I see 200-300ms/instance of nodejs.
What are your experiences? I'm I just doing it wrong :-)
- root_axis 5y ago> Compared to almost any java rendering backends, where I'd expect no more than 50ms response time/thread I see 200-300ms/instance of nodejs. Have not had this experience. Our apps average about 40ms in typical traffic and 70ms under heavy load using SSR with react 16.8, and this is for a full render - in many cases we can serve static or interleaved cached components using ESI to SSR pages in ~20ms.
- brimstedt 5y agoThanks, in gonna have to do some digging :-) Which brings me to the next topic: profiling nodejs apps... Any tips there?
- root_axis 5y agoNode has some basic but decent profiling tools built in, but where I work we use newrelic (enterprise performance monitoring solution) which gives us lots of fine detail about performance bottlenecks in our live systems.
- BenoitEssiambre 5y agofastify.io is supposed to be pretty fast. They do it by minimizing memory allocation. If you're not careful it's very easy to create tons of objects in javascript a common source of slowdowns.