Commit 2af43e66 authored by Sami Kyostila's avatar Sami Kyostila Committed by Commit Bot

Speed up message loop perf test and disable failing waitable event perf test

In order to reduce cycle time on the performance waterfall, drop the
perf test measurement period from 30s to 5s.

Bug: 897751, 848499
Change-Id: I3cd921b327044f02767bc8a43a6e99e5a8a6f48f
Reviewed-on: https://chromium-review.googlesource.com/c/1315967Reviewed-by: default avatarFrançois Doray <fdoray@chromium.org>
Commit-Queue: Sami Kyöstilä <skyostil@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605922}
parent bfc78a0a
......@@ -28,8 +28,7 @@ namespace {
// Tests below will post tasks in a loop until |kPostTaskPerfTestDuration| has
// elapsed.
constexpr TimeDelta kPostTaskPerfTestDuration =
base::TimeDelta::FromSeconds(30);
constexpr TimeDelta kPostTaskPerfTestDuration = base::TimeDelta::FromSeconds(5);
} // namespace
......
......@@ -150,7 +150,8 @@ TEST(WaitableEventPerfTest, MultipleThreads) {
PrintPerfWaitableEvent(&signaler, "_signaler", "multithread-1000-samples");
}
TEST(WaitableEventPerfTest, Throughput) {
// See crbug.com/848499.
TEST(WaitableEventPerfTest, DISABLED_Throughput) {
// Reserve a lot of sample space.
const size_t kCapacity = 500000;
TraceWaitableEvent event(kCapacity);
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment