You're probably right, especially given that these seem to be pure-javascript benchmarks, where Linux shouldn't have any particular disadvantage.
What this misses, and what is the real problem with Firefox on Linux, is rendering performance. XRender, as far as I know, is not quite where it should be. There are two ways to accelerate it, EXA and XAA, and their performance varies greatly by point release of each driver. Throw in compositing, with a different set of interactions across drivers and acceleration architectures, and the whole gamut of misconfigured distributions, and you get an unspeakable mess.
It would be nice if X.org could finish undoing the damage of XFree86's latter days, and get the drivers stable enough that distributors could figure out how to package them properly. Then maybe somebody could do something about the generally unpleasant and slow Linux GUI experience.
What this misses, and what is the real problem with Firefox on Linux, is rendering performance. XRender, as far as I know, is not quite where it should be. There are two ways to accelerate it, EXA and XAA, and their performance varies greatly by point release of each driver. Throw in compositing, with a different set of interactions across drivers and acceleration architectures, and the whole gamut of misconfigured distributions, and you get an unspeakable mess.
It would be nice if X.org could finish undoing the damage of XFree86's latter days, and get the drivers stable enough that distributors could figure out how to package them properly. Then maybe somebody could do something about the generally unpleasant and slow Linux GUI experience.