For some reason, starting tests before gms makes DM run much faster.
authormtklein <mtklein@chromium.org>
Tue, 5 Aug 2014 14:19:46 +0000 (07:19 -0700)
committerCommit bot <commit-bot@chromium.org>
Tue, 5 Aug 2014 14:19:46 +0000 (07:19 -0700)
Must be getting the path ops tests going early helps?

On my desktop,
Release: 50s -> 24s
Debug: 62s -> 40s

BUG=skia:
R=bsalomon@google.com, mtklein@google.com

Author: mtklein@chromium.org

Review URL: https://codereview.chromium.org/435423003

dm/DM.cpp

index 76dc414..6256d0d 100644 (file)
--- a/dm/DM.cpp
+++ b/dm/DM.cpp
@@ -234,8 +234,8 @@ int dm_main() {
              gms.count(), configs.count(), tests.count(), skps.count());
     DM::Reporter reporter;
     DM::TaskRunner tasks(FLAGS_threads, FLAGS_gpuThreads);
-    kick_off_gms(gms, configs, gpuAPI, *expectations, &reporter, &tasks);
     kick_off_tests(tests, &reporter, &tasks);
+    kick_off_gms(gms, configs, gpuAPI, *expectations, &reporter, &tasks);
     kick_off_skps(skps, &reporter, &tasks);
     tasks.wait();