Hacker News new | ask | show | jobs
by wewewedxfgdf 1 day ago
But Firecracker is not compatible with GPU for Chrome, is that right?

That means Chrome is slow - quite the tradeoff.

2 comments

Headless, so there is no screen to composite and no GPU passed into the VM. Firecracker has no GPU passthrough, so GL work falls back to SwiftShader, the software rasterizer. For automation that is fine. The cost is in layout, JS and network, not raster. It only bites on WebGL or canvas heavy pages.
Our browsers beat competitors in performance too. Chrome uses mainly CPU, not GPU

We support GPU via software tho