Public bug reported:

We don't have a native GpuMemoryBuffer implementation in Oxide, instead
falling back to the software implementation (using shared memory).

chrome://tracing/ shows there's a lot of contention for the GPU thread
on the phone, and a not-insignificant cause of this is texture uploads.
Having a native GpuMemoryBuffer implementation would significantly
improve this.

What we needs is a graphics buffer that we can:
- Rasterize directly to
- Share between processes
- Use as a source for EGLImage

https://01.org/blogs/2016/native-one-copy-texture-uploads-for-chrome-OS
has some information about how this is implemented on the various Chrome
platforms.

The attached photo (sorry, no screenshots on Freiza) shows an instance
where the GPU thread is blocked for around 10ms just doing texture
uploads.

** Affects: oxide
     Importance: High
         Status: Triaged

** Attachment added: "IMAG0224.jpg"
   
https://bugs.launchpad.net/bugs/1553302/+attachment/4588520/+files/IMAG0224.jpg

** Changed in: oxide
   Importance: Undecided => Critical

** Changed in: oxide
   Importance: Critical => High

** Changed in: oxide
       Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1553302

Title:
  Native GpuMemoryBuffer implementation for the phone

Status in Oxide:
  Triaged

Bug description:
  We don't have a native GpuMemoryBuffer implementation in Oxide,
  instead falling back to the software implementation (using shared
  memory).

  chrome://tracing/ shows there's a lot of contention for the GPU thread
  on the phone, and a not-insignificant cause of this is texture
  uploads. Having a native GpuMemoryBuffer implementation would
  significantly improve this.

  What we needs is a graphics buffer that we can:
  - Rasterize directly to
  - Share between processes
  - Use as a source for EGLImage

  https://01.org/blogs/2016/native-one-copy-texture-uploads-for-chrome-
  OS has some information about how this is implemented on the various
  Chrome platforms.

  The attached photo (sorry, no screenshots on Freiza) shows an instance
  where the GPU thread is blocked for around 10ms just doing texture
  uploads.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1553302/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to     : ubuntu-webapps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help   : https://help.launchpad.net/ListHelp

Reply via email to