New issue
Advanced search Search tips

Issue 887851 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Oct 5
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.2%-1.7% regression in system_health.memory_desktop at 592367:592404

Project Member Reported by jgruber@chromium.org, Sep 21

Issue description

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

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


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

Android Nexus5 Perf
android-nexus5x-perf
linux-perf

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

system_health.memory_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Cc: jarin@chromium.org
Owner: jarin@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1712e1df640000

Turn on full masking with untrusted-code-mitigations by jarin@chromium.org
https://chromium.googlesource.com/v8/v8/+/6a6f050e18b90d5b498d85455e598ca68b14238f
3.118e+07 → 3.156e+07 (+3.842e+05)

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

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Mergedinto: 887213
Status: Duplicate (was: Assigned)

Sign in to add a comment