11–19 of 19 posts
Thank you to everyone involved in this. I'm wondering, is Node.js fiddling with v8 in order to focus more on the resulting code performance than the initial startup. Planning to learn C/C++ in order to investigate that and if there any gains there.
I would guess node.js apps can load a ton of code so the startup can be important too.
Earlier quoted context omitted.
I would guess node.js apps can load a ton of code so the startup can be important too.
What's a 30 seconds of startup for an app that will stay up for a few hours until the next deploy?
For serverless with cold starts, direct translation to $.
The whole motivation for tiered JITing is to attempt a balance that gets the best of both worlds; fast startup, optimized hot code (over time).
Earlier quoted context omitted.
I would guess node.js apps can load a ton of code so the startup can be important too.
What's a 30 seconds of startup for an app that will stay up for a few hours until the next deploy?
Just read the first sentence if you are thinking I’m being a bit harsh:
“We’ve previously made a case why four tiers in V8(Google internal) make sense to explain why Sparkplug made sense in addition to Ignition, TurboProp and TurboFan. TurboProp was a midtier compiler proposal based on TurboFan to significantly improve compilation speed while compromising on the performance of the resulting code. With Sparkplug in place, however, the design tradeoffs TurboProp made by being built on top of TurboFan didn’t end up panning out. ”