New issue
Advanced search Search tips

Issue 877603 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 877247
Owner:
Closed: Oct 10
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1%-6.6% regression in system_health.memory_mobile at 585103:585240

Project Member Reported by m...@chromium.org, Aug 24

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=877603

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=643573c20db8fadc6d83285ebf2bce4a5ae725f17bcb440d2ef77647a1535f58


Bot(s) for this bug's original alert(s):

Android Nexus5 Perf
Android Nexus6 WebView Perf
android-nexus5x-perf

blink_perf.image_decoder - Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks

system_health.memory_mobile - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

memory.top_10_mobile - Benchmark documentation link:
  None

Comment 3 Deleted

Status: Untriaged (was: WontFix)
Cc: twelling...@chromium.org
Owner: twelling...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/112f3696640000

Remove Modern flag and hardcode #isChromeModernDesignEnabled to true by twellington@chromium.org
https://chromium.googlesource.com/chromium/src/+/5955e6d67f3799a0cdd9dba7df8fa5460499f99f
4.875e+07 → 5.048e+07 (+1.733e+06)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Cc: tedc...@chromium.org mdjones@chromium.org
It looks like this is the same as  issue 877247 , which similarly reported a gpu memory regression when Modern is enabled.

miu@ - is it reasonable to mark this as a duplicate?
Also, the pinpoint job seems to specifically identify system_health.memory_mobile. I would be really surprised if the CL identified affected WebView performance since it was a visual redesign of Clank UI (code primary isolated to chrome/android/java).

Are there other pinpoint jobs need to identify culprits for the other alerts in comment #1?
Owner: m...@chromium.org
miu@ - the pinpoint job in #6 identified a gpu regression that's already covered in  issue 877247 . Will you please confirm whether this bug can be closed or whether more work is needed to investigate the other alerts in the original bug report?
Mergedinto: 877247
Status: Duplicate (was: Assigned)
Sounds reasonable to me.

Sign in to add a comment