On 5/18/2014 3:16 AM, Bas Schouten wrote:
remove a lot of code that we've currently been duplicating. Furthermore it puts
us on track for enabling other features on desktop like APZ, off main thread
animations and other improvements.
What is APZ?
Is OMTC turned on in all graphics setups, accelerated and not? Are we
testing browser performance/responsiveness in these setups?
There's several bugs still open (some more serious than others) which we will
be addressing in the coming weeks, hopefully before the merge to Aurora.
I want to call out one specifically, bug 933733 (and related bug 912521)
which we know is going to regress; we currently don't know how to fix
and we're not sure why it's happening. If anyone experiences the Firefox
UI freezing unless they are moving the mouse, please let us know ASAP in
the bug and we'll work with you to collect trace logs and try and
pinpoint a solution.
- Memory numbers will increase somewhat, this is unavoidable, there's several
steps which have to be taken when doing off main thread compositing (like
double-buffering), which inherently use more memory.
I am concerned about this in general, because we know that OOM is a real
problem for many of our users currently, and we have very poor metrics
on memory usage in the wild. So I have a couple questions:
* Is it a fair statement to say that the primary benefit of OMTC is in
browser responsiveness and jank?
* Are there settings/knobs which which can reduce the memory usage of
this feature (other than disabling OMTC completely)? If so, do we have a
plan for tuning those knobs on beta before this hits release?
* How will we know whether OMTC is a net win for users on low-memory
computers, where increased memory usage and paging might offset the
responsiveness benefits?
* Are there accurate about:memory reporters for OMTC buffers?
--BDS
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
