Initial page load produces 3 compositor commits instead of just 1 |
||||||||
Issue descriptionWhen the Android application is started and the default page (e.g. google.com) is loaded, three full compositor commits are pushed to the client. No user interaction is required. The commits can be seen by running vmodule="blimp_connection=2" on the engine to get detailed info on the outgoing messages. Grepping the log output for "type=COMPOSITOR" isolates the compositor messages from the rest of the noise. The commit messages are distinguishable from other messages by their large value for "byte_size". [1234:1255:0325/150327:VERBOSE2:blimp_connection.cc(66)] Sender::ProcessMessage <BlimpMessage type=COMPOSITOR target_tab_id=0 byte_size=60796> ... [1234:1255:0325/150330:VERBOSE2:blimp_connection.cc(66)] Sender::ProcessMessage <BlimpMessage type=COMPOSITOR target_tab_id=0 byte_size=60781> ... [1234:1255:0325/150331:VERBOSE2:blimp_connection.cc(66)] Sender::ProcessMessage <BlimpMessage type=COMPOSITOR target_tab_id=0 byte_size=61642>
,
Mar 31 2016
,
Mar 31 2016
,
Mar 31 2016
,
Apr 1 2016
,
Apr 1 2016
,
Apr 1 2016
The engine is requesting commits as the page gets invalidated during layout. From an initial investigation into the commit messages when connected to a local engine, I see 5 commits and it looks like a significant chunk of the additional data is from resending images. [1:1:0331/204542:ERROR:remote_channel_main.cc(163)] Starting commit serialization [1:1:0331/204542:ERROR:remote_channel_main.cc(166)] Commit proto size: 9762 [1:1:0331/204542:ERROR:remote_channel_main.cc(163)] Starting commit serialization [1:1:0331/204542:ERROR:blimp_image_serialization_processor.cc(93)] Sending image of size: 7630 [1:1:0331/204542:ERROR:remote_channel_main.cc(166)] Commit proto size: 23964 [1:1:0331/204543:ERROR:remote_channel_main.cc(163)] Starting commit serialization [1:1:0331/204543:ERROR:blimp_image_serialization_processor.cc(89)] Re-sending image of size: 7630 [1:1:0331/204543:ERROR:blimp_image_serialization_processor.cc(93)] Sending image of size: 5100 [1:1:0331/204543:ERROR:blimp_image_serialization_processor.cc(93)] Sending image of size: 35356 [1:1:0331/204543:ERROR:remote_channel_main.cc(166)] Commit proto size: 60848 [1:1:0331/204544:ERROR:remote_channel_main.cc(163)] Starting commit serialization [1:1:0331/204544:ERROR:blimp_image_serialization_processor.cc(89)] Re-sending image of size: 7630 [1:1:0331/204544:ERROR:blimp_image_serialization_processor.cc(89)] Re-sending image of size: 5100 [1:1:0331/204545:ERROR:blimp_image_serialization_processor.cc(89)] Re-sending image of size: 35356 [1:1:0331/204545:ERROR:remote_channel_main.cc(166)] Commit proto size: 60833 [1:1:0331/204545:ERROR:remote_channel_main.cc(163)] Starting commit serialization [1:1:0331/204545:ERROR:blimp_image_serialization_processor.cc(89)] Re-sending image of size: 7630 [1:1:0331/204545:ERROR:blimp_image_serialization_processor.cc(89)] Re-sending image of size: 5100 [1:1:0331/204545:ERROR:blimp_image_serialization_processor.cc(89)] Re-sending image of size: 35356 [1:1:0331/204545:ERROR:remote_channel_main.cc(166)] Commit proto size: 61699 Commit#1 Total: 9762 Commit#2: Total: 23964 Commit#3: Total: 60848 Image Data resent: 7630 Commit#4: Total: 60833 Image Data resent: 48086 Commit#5: Total: 61699 Image Data resent: 48086 crbug/597807 is already tracking image caching which should eliminate these redundant transfers. Other than this, crbug/597816 is tracking investigation into the compositor messages to understand further optimizations to reduce data usage and crbug/599762 is tracking investigation into commit throttling on the engine.
,
Dec 9 2016
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by kmarshall@chromium.org
, Mar 25 2016