[webkit-qt] QtWebKit and SunSpider Benchmark: - are these expected results
jocelyn.turcotte at digia.com
Tue Feb 19 09:32:48 PST 2013
those are cool numbers! I looked at what it would take to get DFG JIT and it seemed like it would take some work.
My main issue is that it would make sense to enable it for 32bit at the same time, and that we should put some testing effort before we release something like this, but we don't have this at reach.
I didn't know that LLINT would give a big improvement in addition to JIT, it's not enabled at all on Windows and it seems like it might be worth looking at before DFG depending on the effort it needs and the risk it introduces.
On Tue, Feb 19, 2013 at 06:06:45PM +0100, Osztrogonác Csaba wrote:
> Jocelyn, have you tried to enable DFG JIT and/or
> LLINT on Windows? Both of them can speedup JSC.
> But I have no idea how MSVC friendly the LLINT asm is ...
> On my Linux box I got the following numbers a week before for SunSpider:
> - interpreter (LLINT C-loop): 836 ms
> - LLINT (asm): 480 ms
> - JIT: 305 ms
> - LLINT + JIT: 193 ms
> - LLINT + JIT + DFG-JIT: 140 ms
> Jocelyn Turcotte írta:
> >Hi Stan,
> >On Windows 32bit it still has basic JIT.
> >On Windows 64bit it lags way behind, where it's still using the interpreter.
> >This patch brings basic JIT support for Windows x64 and should be released with Qt 5.1: https://bugs.webkit.org/show_bug.cgi?id=107965
> >This should be 2x-4x times faster than the interpreter according to my quick tests.
> >But this still doesn't add support for DFG JIT, still only available on Mac and Linux, which would bring JS performances closer to Chrome's.
> >So yes sadly I think that this kind of performance is currently expected on Windows x64 with Qt 5.0.
> webkit-qt mailing list
> webkit-qt at lists.webkit.org
More information about the webkit-qt