GitLab

Based on a conversation I had with Nicole:

If you look at the WebKit code base and the commits for optimizations, a lot of effort has been put into it in the area of Javascript, JIT and more more areas, but with very specific x86 optimizations (like assembly parts, Javascript to x86 assembly JIY etc.). All of that is missing for ARM and this could be the major part of some of the slow downs in performance.

There are some more optimizations specific for WebKit GTK to use OpenGL for more rendering which may not yet be enabled since the OpenGL implementations for ARM are/were not consistent enough. Maybe we can already improve the situation by switching on some compile options for the WebKit and WebKit GTK package.

There are many compile options being used now (see our latest build of webkit), but at least trying trying the compile time switches and playing with the results is something that someone just able to compile these packages could do.

This issue is to track the effort someone spends just looking into the compile options used and investigate if there are others we should be using.