Hacker News Reader

All the tests were done on an n2-standard-2 gcp instance... That doesn't have a GPU. Rendering a webpage without a GPU uses a lot of different codepaths and isn't awfully representative of performance with a GPU.

View on HN

I ran most of the tests on example.com, which is easy to render without having a GPU available.

Looking at on-page CPU time for Evernote, 91% is spent just processing JavaScript or HTML. So I expect any benefit of a GPU to be minimal.

But there might also be a performance hit with a GPU... There are various antipatterns like drawing on a canvas and then reading back the pixels repeatedly that perform atrociously with a GPU (due to the latency between the CPU and GPU). Some sites do a lot of that for things like custom font rendering, fingerprinting user hardware, custom data decompression algorithms that use canvas, etc.

Lab analysis is always going to have compromises. What's important is the relative change (without and with the extensions), and that the extra work isn't especially slowed down because of lack of GPU.

Reply on news.ycombinator.com