1458076 - Nimbledroid's buzzfeed.com page load test is 2x slower in GeckoView than WebView

Status: RESOLVED WORKSFORME

(GeckoView :: General, defect, P2)

Description

[Chris Peterson [:cpeterson]]

Nimbledroid test results:

Klar+WebView = 5.2 seconds

https://nimbledroid.com/my_apps/org.mozilla.focus.debug?a=d78f816d-3591-4203-9820-bed76f107406

Klar+GeckoView = 10.9 seconds

https://nimbledroid.com/my_apps/org.mozilla.klar.gecko.debug?a=aa414153-e579-4f7b-a5ee-850b48f5b70a#summary 

Randell saw similar Firefox performance problems on desktop when profiling abcnews.go.com, so this is not an Android-specific problem. Transferred data is the same (64K). Uncompressed size is 306K. Content is identical, but we took far longer to load the initial HTML and far longer to finish loading the page.

Chrome on desktop:
  redirect is 184  ms
  document is 142ms
  page fully loaded is ~2500 ms

FF local opt build on desktop:
  redirect 85ms
  document takes 1856 ms
  page fully loaded is ~7000-9000 ms

Comment 1

[Chris Peterson [:cpeterson]]

(In reply to Chris Peterson [:cpeterson] from comment #0)
> Randell saw similar Firefox performance problems on desktop when profiling
> abcnews.go.com, so this is not an Android-specific problem.

Correction: this should say "buzzfeed.com", not "abcnews.go.com". Bug 1458073 tracks abcnews.go.com performance. This bug is about buzzfeed.com.

Comment 2

[Mike Conley (:mconley) (:⚙️)]

Hey cpeterson, for the Desktop case, can you provide a profile for us on the machine with the Firefox instance that was seeing the slow load?

Comment 3

[David Bolter [:davidb] (NeedInfo me for attention)]

P2 feels right as a default for performance bugs tied to our nimbledroid informed perf work.

Comment 4

[Chris Peterson [:cpeterson]]

Klar+GV is not blocking tracking scripts correctly (bug 1459037), so we can't fairly compare Focus+WebView vs Klar+GeckoView yet.

Comment 5

[Jean Gong :jgong]

Chris, we would like you to capture a new profile but it's broken right now.

Comment 6

[Chris Peterson [:cpeterson]]

(In reply to Jean Gong :jgong from comment #5)

Chris, we would like you to capture a new profile but it's broken right now.

What is broken? The Buzzfeed link or Gecko profiling?

Here is the Buzzfeed URL used in the Nimbledroid page load tests:

https://www.buzzfeed.com/daves4/the-new-york-times-makes-the-nerdiest-correction-e?utm_term=.tlL2KE08L6

In Firefox 65, the page's loading spinner takes 20+ seconds to stop spinning. In Chrome and Firefox 66 and 67, the loading spinner stops spinning after about 5 seconds. Perhaps Randell's timer changes in 66 fixed this issue?

Comment 7

[Olli Pettay [:smaug][[e-mail]]]

Based on the comment 6, this looks like done.
Please reopen if needed or file new bugs.
WFM (or possibly FIXED)

Comment 8

[Chris Peterson [:cpeterson]]

The Nimbledroid test results for buzzfeed.com say that GeckoView is 18x slower than Chrome (25.10 vs 1.40 seconds). I don't trust these Nimbledroid tests and the Chrome results have not be updated since January. I will ask if there is newer data.

https://health.graphics/android/graph?site=https://www.buzzfeed.com/daves4/the-new-york-times-makes-the-nerdiest-correction-e?utm_term=.tlL2KE08L6#.hwrBglaV2A

Comment 9

[Chris Peterson [:cpeterson]]

WFM

Manual comparison of the time to load the full page on my Moto G5 for https://www.buzzfeed.com/daves4/the-new-york-times-makes-the-nerdiest-correction-e

Fennec 68 Nightly: about 2 seconds
Fenix (GV 67 Beta): about 2 seconds
Chrome 73: about 1 second