[wpe-webkit] Optimising imx6 performance for HTML5 using Cog + WPE WebKit

Wouter Vanhauwaert W.Vanhauwaert at TELEVIC.com
Tue Oct 29 03:01:17 PDT 2019

> -----Original Message-----
> From: Andy Pont [mailto:andy.pont at sdcsystems.com]
> Sent: dinsdag 29 oktober 2019 10:46
> To: Wouter Vanhauwaert <W.Vanhauwaert at TELEVIC.com>
> Cc: webkit-wpe at lists.webkit.org
> Subject: Re: [wpe-webkit] Optimising imx6 performance for HTML5 using Cog +
> WPE WebKit
> Wouter wrote...
> >Problem with 'interface based on HTML5, javascript and CSS', is that it can be
> done in a thousand ways...
> >Some of them will fall back to hardware, and some of them will need
> calculation so take CPU time.
> >Without an insight in a code-abstraction, it's impossible to tell what the issue
> is.
> I’ll see what I can find out from our customer as to how they have implemented
> the animations. The test code I have is all obfuscated but as far as I can tell it is
> all based around the vue.js framework and the Vuex state management library.

I think you have your culprit there. 
I don't know vue.js myself, but these frameworks are normally not optimized for embedded systems. They are good in hiding all the logics and presenting an "easy interface" for the programmer. However, as it's a .js library, I could imagine that a move for instance is a loop of changing a position by X-steps => cpu intensive.
Where you should do a translate3d => done by GPU, so barely CPU usage

But I know the feeling of persuading a client to do it differently. After all, it's working fine on that chromium browser on a pc ;-)


More information about the webkit-wpe mailing list