|
|
Chromium Code Reviews|
Created:
4 years, 8 months ago by Camillo Bruni Modified:
4 years, 8 months ago CC:
chromium-reviews, Michael Hablich, telemetry-reviews_chromium.org Base URL:
https://chromium.googlesource.com/chromium/src.git@master Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
Description[perf] Add speedometer-ignition benchmark
BUG=chromium:593793
LOG=n
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:mac_retina_perf_cq;tryserver.chromium.perf:linux_perf_cq
Committed: https://crrev.com/0a791019658bc90c48afb894f3481952ac403c5f
Cr-Commit-Position: refs/heads/master@{#387921}
Patch Set 1 #
Total comments: 4
Patch Set 2 : including v8_helper and addressing pylint issues #Patch Set 3 : resolve merge conflicts #Patch Set 4 : merge master #
Messages
Total messages: 50 (22 generated)
Description was changed from ========== [perf] Adding speedometer-ignition benchmark BUG= ========== to ========== [perf] Adding speedometer-ignition benchmark BUG= CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:android_s5_perf_cq;tryserver.chromium.perf:winx64_10_perf_cq;tryserver.chromium.perf:mac_retina_perf_cq;tryserver.chromium.perf:linux_perf_cq ==========
The CQ bit was checked by cbruni@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1860013002/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1860013002/1
cbruni@chromium.org changed reviewers: + nednguyen@google.com, samistil@chromium.org
PTAL We figure that we should have the speedometer benchmark running with --ignition on (our interpreter) to estimate the impact of our changes.
https://codereview.chromium.org/1860013002/diff/1/tools/perf/benchmarks/speed... File tools/perf/benchmarks/speedometer.py (right): https://codereview.chromium.org/1860013002/diff/1/tools/perf/benchmarks/speed... tools/perf/benchmarks/speedometer.py:31: import v8_helper Did you forgot to check in this file? I can't find it in code search: https://code.google.com/p/chromium/codesearch#search/&q=v8_helper.py&sq=packa... https://codereview.chromium.org/1860013002/diff/1/tools/perf/benchmarks/v8.py File tools/perf/benchmarks/v8.py (right): https://codereview.chromium.org/1860013002/diff/1/tools/perf/benchmarks/v8.py... tools/perf/benchmarks/v8.py:26: def CreateV8TimelineBasedMeasurementOptions(benchmark): You don't need the benchmark param. Did the pylint warn about unused param? If not, lemme know since it's probably a bug. Also to remove the boiler plates in benchmarks that use this, you can create s.t like _TimelineBasedV8Benchmark with CreateTimelineBasedMeasurementOptions(self) being this one & have your other v8 benchmarks subclass it.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: chromium_presubmit on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)
https://codereview.chromium.org/1860013002/diff/1/tools/perf/benchmarks/speed... File tools/perf/benchmarks/speedometer.py (right): https://codereview.chromium.org/1860013002/diff/1/tools/perf/benchmarks/speed... tools/perf/benchmarks/speedometer.py:31: import v8_helper On 2016/04/05 at 14:43:16, nednguyen wrote: > Did you forgot to check in this file? I can't find it in code search: https://code.google.com/p/chromium/codesearch#search/&q=v8_helper.py&sq=packa... bah... yes :D https://codereview.chromium.org/1860013002/diff/1/tools/perf/benchmarks/v8.py File tools/perf/benchmarks/v8.py (right): https://codereview.chromium.org/1860013002/diff/1/tools/perf/benchmarks/v8.py... tools/perf/benchmarks/v8.py:26: def CreateV8TimelineBasedMeasurementOptions(benchmark): On 2016/04/05 at 14:43:16, nednguyen wrote: > You don't need the benchmark param. Did the pylint warn about unused param? If not, lemme know since it's probably a bug. > > Also to remove the boiler plates in benchmarks that use this, you can create s.t like _TimelineBasedV8Benchmark with CreateTimelineBasedMeasurementOptions(self) being this one & have your other v8 benchmarks subclass it. since I accidentally created v8_helper.py in the current working directory the pylint messages didn't make sense, corrected that now.
rmcilroy@chromium.org changed reviewers: + rmcilroy@chromium.org
+1 to adding Speedometer (thanks!) but could we fix the V8 execution metrics before adding more benchmarks that depend on them? The numbers for compiling / parsing / execution are completely bogus due to crbug.com/596405.
On 2016/04/06 at 08:35:12, rmcilroy wrote: > +1 to adding Speedometer (thanks!) but could we fix the V8 execution metrics before adding more benchmarks that depend > on them? The numbers for compiling / parsing / execution are completely bogus due to crbug.com/596405. This is only for the speedometer results, not our trace-based telemetry measurements. TBM v2. is in the pipeline, see https://github.com/catapult-project/catapult/issues/2190
On 2016/04/06 09:18:26, Camillo Bruni wrote: > On 2016/04/06 at 08:35:12, rmcilroy wrote: > > +1 to adding Speedometer (thanks!) but could we fix the V8 execution metrics > before adding more benchmarks that depend > > on them? The numbers for compiling / parsing / execution are completely bogus > due to crbug.com/596405. > > This is only for the speedometer results, not our trace-based telemetry > measurements. > TBM v2. is in the pipeline, see > https://github.com/catapult-project/catapult/issues/2190 Ahh right, sounds good - I mistook the changes in v8.py as being related to the speedometer benchmark, not just refactoring related to pulling out the ignition option. Thanks.
PTAL again
The CQ bit was checked by cbruni@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1860013002/20001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1860013002/20001
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: mac_chromium_compile_dbg_ng on tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...) mac_chromium_gn_rel on tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_gn_r...) mac_chromium_rel_ng on tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)
The CQ bit was checked by cbruni@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1860013002/40001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1860013002/40001
On 2016/04/07 13:20:52, commit-bot: I haz the power wrote: > Dry run: CQ is trying da patch. Follow status at > https://chromium-cq-status.appspot.com/patch-status/1860013002/40001 > View timeline at > https://chromium-cq-status.appspot.com/patch-timeline/1860013002/40001 lgtm Nits on the description title: "Add" instead of "Adding"
Description was changed from ========== [perf] Adding speedometer-ignition benchmark BUG= CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:android_s5_perf_cq;tryserver.chromium.perf:winx64_10_perf_cq;tryserver.chromium.perf:mac_retina_perf_cq;tryserver.chromium.perf:linux_perf_cq ========== to ========== [perf] Add speedometer-ignition benchmark BUG= CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:android_s5_perf_cq;tryserver.chromium.perf:winx64_10_perf_cq;tryserver.chromium.perf:mac_retina_perf_cq;tryserver.chromium.perf:linux_perf_cq ==========
updated description title
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: android_s5_perf_cq on tryserver.chromium.perf (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_...)
The CQ bit was checked by cbruni@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1860013002/40001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1860013002/40001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_s5_perf_cq on tryserver.chromium.perf (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_...)
On 2016/04/08 at 10:00:40, commit-bot wrote: > Try jobs failed on following builders: > android_s5_perf_cq on tryserver.chromium.perf (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_...) Do you have any clue why the android build would time out? I noticed locally that the TBM v2 run a bit slower on longer traces and the adwords benchmark is rather big.
Description was changed from ========== [perf] Add speedometer-ignition benchmark BUG= CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:android_s5_perf_cq;tryserver.chromium.perf:winx64_10_perf_cq;tryserver.chromium.perf:mac_retina_perf_cq;tryserver.chromium.perf:linux_perf_cq ========== to ========== [perf] Add speedometer-ignition benchmark BUG=chromium:593793 LOG=n CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:android_s5_perf_cq;tryserver.chromium.perf:winx64_10_perf_cq;tryserver.chromium.perf:mac_retina_perf_cq;tryserver.chromium.perf:linux_perf_cq ==========
The CQ bit was checked by cbruni@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1860013002/60001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1860013002/60001
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: android_s5_perf_cq on tryserver.chromium.perf (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_...)
On 2016/04/15 14:01:54, commit-bot: I haz the power wrote: > Dry run: Try jobs failed on following builders: > android_s5_perf_cq on tryserver.chromium.perf (JOB_FAILED, > http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_...) If you think the failure of android_s5_perf_cq is unrelated, I would just remove it from the CQ_EXTRA_TRYBOT list
Description was changed from ========== [perf] Add speedometer-ignition benchmark BUG=chromium:593793 LOG=n CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:android_s5_perf_cq;tryserver.chromium.perf:winx64_10_perf_cq;tryserver.chromium.perf:mac_retina_perf_cq;tryserver.chromium.perf:linux_perf_cq ========== to ========== [perf] Add speedometer-ignition benchmark BUG=chromium:593793 LOG=n CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:winx64_10_perf_cq;tryserver.chromium.perf:mac_retina_perf_cq;tryserver.chromium.perf:linux_perf_cq ==========
The CQ bit was checked by cbruni@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from nednguyen@google.com Link to the patchset: https://codereview.chromium.org/1860013002/#ps60001 (title: "merge master")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1860013002/60001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1860013002/60001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: winx64_10_perf_cq on tryserver.chromium.perf (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_10_perf_c...)
The CQ bit was checked by nednguyen@google.com
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1860013002/60001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1860013002/60001
On 2016/04/18 14:48:45, commit-bot: I haz the power wrote: > CQ is trying da patch. Follow status at > https://chromium-cq-status.appspot.com/patch-status/1860013002/60001 > View timeline at > https://chromium-cq-status.appspot.com/patch-timeline/1860013002/60001 If perf:winx64_10_perf_cq is causing problem again, I would also remove them. Sorry for the annoyance!
Description was changed from ========== [perf] Add speedometer-ignition benchmark BUG=chromium:593793 LOG=n CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:winx64_10_perf_cq;tryserver.chromium.perf:mac_retina_perf_cq;tryserver.chromium.perf:linux_perf_cq ========== to ========== [perf] Add speedometer-ignition benchmark BUG=chromium:593793 LOG=n CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:mac_retina_perf_cq;tryserver.chromium.perf:linux_perf_cq ==========
Message was sent while issue was closed.
Committed patchset #4 (id:60001)
Message was sent while issue was closed.
Description was changed from ========== [perf] Add speedometer-ignition benchmark BUG=chromium:593793 LOG=n CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:mac_retina_perf_cq;tryserver.chromium.perf:linux_perf_cq ========== to ========== [perf] Add speedometer-ignition benchmark BUG=chromium:593793 LOG=n CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:mac_retina_perf_cq;tryserver.chromium.perf:linux_perf_cq Committed: https://crrev.com/0a791019658bc90c48afb894f3481952ac403c5f Cr-Commit-Position: refs/heads/master@{#387921} ==========
Message was sent while issue was closed.
Patchset 4 (id:??) landed as https://crrev.com/0a791019658bc90c48afb894f3481952ac403c5f Cr-Commit-Position: refs/heads/master@{#387921} |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
