New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 887374 link

Starred by 1 user
Status: WontFix
Owner:
kylec...@chromium.org
Closed: Sep 24
Cc:
kylec...@chromium.org
█ alexclarke@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

33.4%-54.4% improvement in system_health.memory_desktop at 591411:591464

Project Member Reported by alexclarke@chromium.org, Sep 20 
Suspiciously large improvement.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 20 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=887374

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


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

linux-perf

system_health.memory_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 22

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

Improve GL texture memory reporting. by kylechar@chromium.org
https://chromium.googlesource.com/chromium/src/+/d167a866a8f6c4d270830501a6fbd623128a32ad
2.538e+07 → 1.788e+07 (-7.491e+06)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

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

Comment 4 by kylec...@chromium.org, Sep 24

Status: WontFix (was: Assigned)
This is expected due to fixing double counting tile memory between the display compositor and browser/renderer that allocated the tile memory.
►

Sign in to add a comment