One Shot Code Optimization improvements Tracking |
|||
Issue description
,
Aug 22
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/147e1016640000
,
Aug 22
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/147a289a640000
,
Aug 22
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/17e2f34e640000
,
Aug 22
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/147a289a640000 [cpu-profiler] Separate the flags for generating extra line information by petermarshall@chromium.org https://chromium.googlesource.com/v8/v8/+/30ff6719db441cc7ef220d449970cc169067e256 5.452e+06 → 5.336e+06 (-1.161e+05) Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Aug 22
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/147e1016640000 Enable one shot flag by default by chandanreddy@google.com https://chromium.googlesource.com/v8/v8/+/29a112bbadd19eed748806f3391aff4466460050 1.016e+07 → 9.609e+06 (-5.491e+05) Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Aug 30
,
Aug 30
The won't fix here is for the improvements right? Do we have a separate bug for the regressions?
,
Aug 30
Yes, just the improvements! I wanted to track down a few places that were not directly visible on the graphs. |
|||
►
Sign in to add a comment |
|||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 22