Re:Why Google Sheets ported its calculation worker from Java...
by tjlav5 on Thursday June 27, 2024 @09:08AM
(#40810087)
It’s perhaps telling that they had an initial prototype which was 2x slower, then talk about specific optimization strategies but never share the updated overall speed comparison.
[ Parent
| on HN ]
Re:Why Google Sheets ported its calculation worker from Java...
by bluk on Thursday June 27, 2024 @09:17AM
(#40810168)
In a different blog:
https://workspace.google.com/blog/sheets/new-innovations-in-...
"Building on improvements like smooth scrolling and expanded cell limits in Sheets, today we’re announcing that we’ve doubled the speed of calculation in Sheets on Google Chrome and Microsoft Edge browsers,"...
I assume this is 2x the speed of their current JavaScript code.
Re:Why Google Sheets ported its calculation worker from Java...
by azakai on Thursday June 27, 2024 @11:57AM
(#40811917)
Yes, that is correct. It began 2x slower than JS, and ended up 2x faster than JS.
Re:Why Google Sheets ported its calculation worker from Java...
by notRobot on Thursday June 27, 2024 @05:42PM
(#40815444)
I'm sorry I'm bad with translating numbers. This means originally the new version ran at half the speed of the JS version, but ended up running at double the speed? Pretty cool.
Re:Why Google Sheets ported its calculation worker from Java...
by azakai on Thursday June 27, 2024 @06:46PM
(#40816007)
Yeah, exactly. The initial prototype turned out to be quite slow - a lot of optimizations are needed to be fast. The version as of now is 4x faster than that initial prototype, and 2x faster than the JS version. And we are working to make it even faster.
The good news is that most of those optimizations weren't specific to Java, like work in V8 (that helps any Chromium-based-browser running WasmGC) and work in Binaryen (that helps any Binaryen-using toolchain, like Kotlin and Dart).