Fennec/NativeUI/checkerboarding: Difference between revisions

no edit summary
No edit summary
 
(8 intermediate revisions by 5 users not shown)
Line 14: Line 14:
#** 6ms buffer rotation  
#** 6ms buffer rotation  
# Zoomed in panning on nytimes.com: http://bit.ly/HdceNy
# Zoomed in panning on nytimes.com: http://bit.ly/HdceNy
#* 34m PresShell::Paint
#* 34ms PresShell::Paint
#** 5ms displaylist building
#** 5ms displaylist building
#** 2ms compute visibility
#** 2ms compute visibility
Line 23: Line 23:
# Zoom out on nytimes.com: http://bit.ly/HjC3eD (409ms paint) http://bit.ly/HIMqas (371ms paint)
# Zoom out on nytimes.com: http://bit.ly/HjC3eD (409ms paint) http://bit.ly/HIMqas (371ms paint)
#* mostly drawing text. We run into {{bug|742134}}
#* mostly drawing text. We run into {{bug|742134}}


* Painting
* Painting
Line 30: Line 33:


=== Work in progress ===
=== Work in progress ===
* Fixing up touch overhead at the beginning of pans (Some set of bugs) (kats)
* Fixing up touch overhead at the beginning of pans - {{bug|740883}} and dependent bugs (kats)
* TiledThebesLayer {{bug|739679}} (bgirard) - This will help remove buffer rotation overhead and will make it so we can resize the display port with less cost.
* TiledThebesLayer {{bug|739679}} (bgirard) - This will help remove buffer rotation overhead and will make it so we can resize the display port with less cost.
* 16 bit drawing {{bug|733607}} (roc)
* 16 bit drawing {{bug|733607}} (roc)
Line 51: Line 54:


==== Other ideas? ====
==== Other ideas? ====
* Building database of common pages/gestures
* On-demand/interruptable drawing (depends somewhat on tiles)


==Pan/Zoom Jank==
==Pan/Zoom Jank==
Line 74: Line 79:
* Native browser on Gingerbread won't ever checkerboard it just paints slower
* Native browser on Gingerbread won't ever checkerboard it just paints slower
* XUL and native fennec run the page at different zoom levels and scroll to different locations
* XUL and native fennec run the page at different zoom levels and scroll to different locations
* Eideticker is useful for cross-browser comparisons, but should we consider using other/methods tools (i.e. ones that don't require specialized hardware) as well?
* Eideticker is useful for cross-browser comparisons, but should we consider using other/methods tools (i.e. ones that don't require specialized hardware) for testing performance as well?
* Tracking FPS of scroll & zoom would be most useful.


== When are we done? ==
== When are we done? ==
* What criteria do we have for being good enough?
* What criteria do we have for being good enough?
* Not checkerboarding too much!
Confirmed users
523

edits