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

Issue 815264 link

Starred by 2 users
Status: Duplicate
Owner:
█ mariakho...@chromium.org
Left Chrome team
Closed: Feb 2018
Cc:
perezju@chromium.org
█ iannucci@chromium.org
bmeu...@chromium.org
mvstan...@chromium.org
jgruber@chromium.org
dpranke@chromium.org
█ mariakho...@chromium.org
tdres...@chromium.org
rmcilroy@chromium.org
asvitk...@chromium.org
sigurds@chromium.org
mstarzinger@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug-Regression



Sign in to add a comment

1%-7.6% regression in system_health.memory_mobile at 538549:538644

Project Member Reported by tdres...@chromium.org, Feb 23 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Feb 23 2018 

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

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


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

android-nexus5
android-nexus6

Comment 3 by tdres...@chromium.org, Feb 23 2018

Cc: -tdresser@google.com tdres...@chromium.org

Comment 4 by perezju@chromium.org, Feb 26 2018

Cc: perezju@chromium.org
Labels: -Pri-2 Pri-1
This regression is showing up in system health plan (c.f. issue 816412 downstream).

Comment 6 by tdres...@chromium.org, Feb 26 2018 

sullivan, simonhatch, dtu: Pinpoint didn't report back that it failed to reproduce this regression.

I've kicked off another bisect.

Comment 7 by perezju@chromium.org, Feb 26 2018

Cc: mariakho...@chromium.org
From the range this is probably the same as issue 815149 (found on downstream bots).

Comment 8 by mariakho...@chromium.org, Feb 26 2018

Mergedinto: 815149
Status: Duplicate (was: Untriaged)
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Feb 27 2018

Cc: dpranke@chromium.org mstarzinger@chromium.org jgruber@chromium.org tandrii@chromium.org iannucci@chromium.org rmcilroy@chromium.org bmeu...@chromium.org mvstan...@chromium.org sigurds@chromium.org
Owner: iannucci@chromium.org
Status: Assigned (was: Duplicate)
📍 Found significant differences after each of 3 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/1285a448440000

Internalize string constants in code assembler by jgruber@chromium.org
https://chromium.googlesource.com/v8/v8/+/7a80dbdbec2c3e277bdf30c8dcc77431d0761573

[cleanup] Introduce a dedicated FeedbackCell. by bmeurer@chromium.org
https://chromium.googlesource.com/v8/v8/+/aff1f3788b7abce54a27fac750f13f88f240d327

[test_env.py] Reland: Warm up vpython virtualenv cache on swarming task shards by iannucci@chromium.org
https://chromium.googlesource.com/chromium/src/+/2181305023501418e22e421c3ad7a2ecb0322b4d

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

Comment 10 by tandrii@chromium.org, Feb 27 2018

Cc: -tandrii@chromium.org

Comment 11 by jgruber@chromium.org, Feb 27 2018 

The bisect result in #9 (https://chromeperf.appspot.com/group_report?sid=f9e1d84a8da278c2ee71fff07fbbaaaf1bc8c7ebba37f414a7129e128f97e592) seems to have a different root cause than the other graphs in this bug. It looks like a real issue in V8 to me.

Splitting these out into https://crbug.com/816813.
Project Member

Comment 13 by 42576172...@developer.gserviceaccount.com, Feb 27 2018

Cc: asvitk...@chromium.org
Owner: mariakho...@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12fe6668440000

Add MemoryAblation to field_trial_config by mariakhomenko@chromium.org
https://chromium.googlesource.com/chromium/src/+/68d7343808bf1b2cdbdf503ec954b3a6f90987fa

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

Comment 14 by perezju@chromium.org, Feb 27 2018

Status: Duplicate (was: Assigned)
►

Sign in to add a comment