diff options
author | mtklein <mtklein@chromium.org> | 2014-09-03 14:06:47 -0700 |
---|---|---|
committer | Commit bot <commit-bot@chromium.org> | 2014-09-03 14:06:48 -0700 |
commit | 9c7207b5dc71dc5a96a2eb107d401133333d5b6f (patch) | |
tree | d4a19230e5516cb03513c5ad15ab9779dc3eeac0 /dm/DMTestTask.cpp | |
parent | 00b76bd750e668a6989dd497313e715d1b476fdc (diff) |
SkThreadPool ~~> SkTaskGroup
SkTaskGroup is like SkThreadPool except the threads stay in
one global pool. Each SkTaskGroup itself is tiny (4 bytes)
and its wait() method applies only to tasks add()ed to that
instance, not the whole thread pool.
This means we don't need to bring up new thread pools when
tests themselves want to use multithreading (e.g. pathops,
quilt). We just create a new SkTaskGroup and wait for that
to complete. This should be more efficient, and allow us
to expand where we use threads to really latency sensitive
places. E.g. we can probably now use these in nanobench
for CPU .skp rendering.
Now that all threads are sharing the same pool, I think we
can remove most of the custom mechanism pathops tests use
to control threading. They'll just ride on the global pool
with all other tests now.
This (temporarily?) removes the GPU multithreading feature
from DM, which we don't use.
On my desktop, DM runs a little faster (57s -> 55s) in
Debug, and a lot faster in Release (36s -> 24s). The bots
show speedups of similar proportions, cutting more than a
minute off the N4/Release and Win7/Debug runtimes.
BUG=skia:
R=caryclark@google.com, bsalomon@google.com, bungeman@google.com, mtklein@google.com, reed@google.com
Author: mtklein@chromium.org
Review URL: https://codereview.chromium.org/531653002
Diffstat (limited to 'dm/DMTestTask.cpp')
-rw-r--r-- | dm/DMTestTask.cpp | 8 |
1 files changed, 1 insertions, 7 deletions
diff --git a/dm/DMTestTask.cpp b/dm/DMTestTask.cpp index 9e7f41e7d0..ad0c3fb4f3 100644 --- a/dm/DMTestTask.cpp +++ b/dm/DMTestTask.cpp @@ -3,17 +3,11 @@ #include "SkCommandLineFlags.h" #include "SkCommonFlags.h" -// When PathOps threaded tests get going, they're briefly a big consumer of lots of RAM. -// We disable the internal threading there by default on 32-bit builds. -static const bool is32Bit = sizeof(void*) == 4; - -DEFINE_bool2(pathOpsExtended, x, false, "Run extended pathOps tests."); -DEFINE_bool2(pathOpsSingleThread, z, is32Bit, "Disallow pathOps tests from using threads."); +DEFINE_bool2(pathOpsExtended, x, false, "Run extended pathOps tests."); namespace DM { bool TestReporter::allowExtendedTest() const { return FLAGS_pathOpsExtended; } -bool TestReporter::allowThreaded() const { return !FLAGS_pathOpsSingleThread; } bool TestReporter::verbose() const { return FLAGS_veryVerbose; } static SkString test_name(const char* name) { |