Case Study: Npm uses Rust for its CPU-bound bottlenecks [pdf]
1–10 of 307 posts
Re: Case Study: Npm uses Rust for its CPU-bound bottlenecks [pdf]
#2A better title would be the subtitle of the article: "The npm Registry uses Rust for its CPU-bound bottlenecks".
Note that only one service (authentication) was rewritten from node to Rust.
Re: Case Study: Npm uses Rust for its CPU-bound bottlenecks [pdf]
#3No surprise here, good language design pays off for real world applications especially at scale like the NPM infra.
Re: Case Study: Npm uses Rust for its CPU-bound bottlenecks [pdf]
#4Didn’t knew NPM had a speed issue.
Re: Case Study: Npm uses Rust for its CPU-bound bottlenecks [pdf]
#5Title could be improved, as I was wondering if the command line tool npm had itself been rewritten.
It’s actually one of npm’s web services that was rewritten.
FTA: “Java was excluded from consideration because of the requirement of deploying the JVM and associated libraries along with any program to their production servers. This was an amount of operational complexity and resource overhead that was as undesirable as the unsafety of C or C++.”
I find this comparison a bit odd. Even if not using containers, the JVM isn’t hard to deploy as distro package managers include it. Unless a team is managing servers manually rather than an automated tool this doesn’t seem that complex. Am I missing something here?
Re: Case Study: Npm uses Rust for its CPU-bound bottlenecks [pdf]
#6Title could be improved, as I was wondering if the command line tool npm had itself been rewritten. It’s actually one of npm’s web services that was rewritten. FTA: “Java was excluded from consideration because of the requirement of deploying the JVM and associated libraries along with any program to their production servers. This was an amount of operational complexity and resource overhead that was as undesirable a…
If I have a choice between dealing with it and not I’ll choose not every time. It’s an annoying dependency that got even more annoying when Oracle decided to be a pain in the ass. Just because something is “easy” doesn’t mean it’s easier than the alternative.
Re: Case Study: Npm uses Rust for its CPU-bound bottlenecks [pdf]
#7Editorialized title. Don't do that.
Re: Case Study: Npm uses Rust for its CPU-bound bottlenecks [pdf]
#8Title could be improved, as I was wondering if the command line tool npm had itself been rewritten. It’s actually one of npm’s web services that was rewritten. FTA: “Java was excluded from consideration because of the requirement of deploying the JVM and associated libraries along with any program to their production servers. This was an amount of operational complexity and resource overhead that was as undesirable a…
JVM tuning (especially the GC and memory allocation scaling) can be a huge PITA.
Re: Case Study: Npm uses Rust for its CPU-bound bottlenecks [pdf]
#9Title could be improved, as I was wondering if the command line tool npm had itself been rewritten. It’s actually one of npm’s web services that was rewritten. FTA: “Java was excluded from consideration because of the requirement of deploying the JVM and associated libraries along with any program to their production servers. This was an amount of operational complexity and resource overhead that was as undesirable a…
Yeah. I can see the Java issue as a minor annoyance, but to put it on the same level as the lack of safety with C/C++ seems hyperbolic to me.
Re: Case Study: Npm uses Rust for its CPU-bound bottlenecks [pdf]
#10This entire article is a pretty damning report on JavaScript in general, but this sentence takes the cake (emphasis mine):
> The process of deploying the new Rust service was straight-forward, and soon they were able to forget about the Rust service because it caused so few operational issues. At npm, the usual experience of deploying a JavaScript service to production was that the service would need extensive monitoring for errors and excessive resource usage necessitating debugging and restarts.
Is this satire?