Hi, Thank you guys for your great work!
It seems that setting GPU rastarization off is a big performance hit. In Crosswalk 13 GPU rastar is disabled for some devices (e.g. Galaxy S2) but for the same devices it's enabled in Chrome and seems to work OK. There is a huge difference in performance (specifically, in painting time) when setting GPU rastar on/off. See detailed explanation in https://crosswalk-project.org/jira/browse/XWALK-3614 (my comment from today). Just to extend on this a bit more, we see differences in performance between Crosswalk and chrome (in favor to Chrome) in other places. For example, we see on Nexus 10 (Android 5.1) that our game runs on 4FPS (!) when using Crosswalk 13 and 50-60 FPS on Chrome 43. Up to Crosswalk 10 we had similar FPS (is it related to https://www.scirra.com/forum/crosswalk-performance-mega-thread_t125842?) The performance issue is currently the most painful and critical for us (actually, it's also true for anyone I know that is using Crosswalk, or anyone that intends to use it but doesn't because of performance concerns). I would expect Crosswalk to have a performance at least as good as the corresponding Chrome. Why GPU rastarization is set off (for some device) in Crosswalk 13 but is enabled in Chrome and works fine? Also, is there any improvement in regard to the subject in https://www.scirra.com/forum/crosswalk-performance-mega-thread_t125842? Looking forward to get updates on this. Thanks! Dan
_______________________________________________ Crosswalk-help mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help
