Databases
StackOverflow2013
Postsdbo
POAndroid 4.3 On-screen GPU profiling - long gfx waiting time
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAndroid 4.3 On-screen GPU profiling - long gfx waiting time
    primarykey
    data
    text
    <p>I have just updated a Galaxy Nexus to 4.3 and enabled the new On-screen GPU profiling function, and see the following result for Android setup screen:</p> <p><img src="https://i.stack.imgur.com/WB70el.png" alt="enter image description here"></p> <p>According to the <a href="http://developer.android.com/about/versions/jelly-bean.html" rel="nofollow noreferrer">platform highlights</a>: </p> <pre><code>[With] colors indicating time spent creating drawing commands (blue), issuing the commands (orange), and waiting for the commands to complete (yellow). </code></pre> <p>Even on a very simple screen, there are many instances that the screen refresh time is above the threshold for a smooth 60 fps (green line), and it's mostly because there are many instances where a refresh would spend a significant time waiting for the commands to complete (yellow line*), while other times this step is almost instantaneous. This is not something particular to the Setting app either, but seem to be present for all the apps I've tested so far. *looks more orange than yellow to me</p> <p>What I wish to know are:</p> <ol> <li>Is this time spent "waiting for the commands to complete" means that the screen commands are being actively process and thus the time would accurately represent the time spent drawing the screen. <em>OR</em> does this time include the time waiting for video-sync (though I'd think triple buffer would be used to remove this requirement)?</li> <li>The time spent "waiting for the commands to complete" would fluctuate wildly even when drawing the same screen (scroll slightly up &amp; down on the same ScrollView), is there any guidance on how to reduce this fluctuation (or if it could be reduced at all)?</li> </ol> <p><strong>[Edit:]</strong></p> <p>Updated Nexus 7 as well, and it's even worse:</p> <p><img src="https://i.stack.imgur.com/t5KaY.png" alt="enter image description here"></p> <p>As many as 5 frames are being skipped "waiting for the commands to complete" and it really showed in usage, the app was very choppy and unresponsive.</p> <p><strong>[Edit 2:]</strong> I have performed these per <a href="http://www.examiner.com/article/android-4-3-adds-trim-support-alleviating-nexus-7-slowdown-over-time-woes" rel="nofollow noreferrer">this article</a> to trigger TRIM for ~3 days, so the N7 should be as "pristine" as it's going to get short of a factory reset.</p> <ul> <li>The device has been idle for over an hour</li> <li>No idle maintenance window event has been performed in the last 24 hours</li> <li>The device is either being charged with 30 percent battery or it has 80 percent battery</li> </ul> <p>Now Google Maps seem to behave a bit better (see below), so some of the issues may be related to flash access speed though I don't know how.</p> <p><img src="https://i.stack.imgur.com/b3cQb.png" alt="enter image description here"></p> <p>Still, since the Galaxy Nexus is factory reset, its long "waiting for the commands to complete" time can't be related to the lack of TRIM command, and following the above steps indeed didn't produce improvements. So we are back at square one...</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USKai
    1. USKai
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAndroid 4.3 On-screen GPU profiling - long gfx waiting time
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POAndroid 4.3 On-screen GPU profiling - long gfx waiting time
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POAndroid 4.3 On-screen GPU profiling - long gfx waiting time
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO@Yume117 it's mostly minor updates, so don't expect your world to explode in awesomeness :P
      singulars
      1. POAndroid 4.3 On-screen GPU profiling - long gfx waiting time
      1. USKai
    2. COGood question. I don't have the same graphs ( i got a GN too ) but I'm seeing heavy inconsistencies in the home screen. How could rendering the same thing take x ms and then 3-5x ? I wish I could have a "disable java" option :|
      singulars
      1. POAndroid 4.3 On-screen GPU profiling - long gfx waiting time
      1. USRelativeGames
    3. CORegarding #2, is this an observer effect? Does turning off profiling change the choppiness/lag at all?
      singulars
      1. POAndroid 4.3 On-screen GPU profiling - long gfx waiting time
      1. USGeobits
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload