+day macha+

I assume he’s not a benchmark pro, but he did a decent job already. We can
nitpick his sampling methodology - but it won’t change the result. He is correct that many procs is far more memory consuming than single proc, and we already knew this.

This is a tradeoff we made consciously and deliberately. When firefox crashes, all tabs go down. When firefox memory is compromised (security), all tabs are compromised. In chrome, we don’t have those problems, but instead use more RAM. Further, Chrome is also able to implement per-tab prioritization, so that background tabs don’t make foreground tabs go slow. Firefox can’t do that.