skia2/dm
commit-bot@chromium.org 38aeb0fd7a DM: also run benches once.
Also:
  - make GrMemoryPoolBenches threadsafe
  - some tweaks to various DM code
  - rename GM::shortName() to getName() to match benches and tests

On my desktop, (289 GMs, 617 benches) x 4 configs, 227 tests takes 46s in Debug, 14s in Release.  (Still minutes faster than running tests && bench && gm.)  GPU singlethreading is definitely the limiting factor again; going to reexamine whether that's helpful to thread it again.

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

Author: mtklein@chromium.org

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

git-svn-id: http://skia.googlecode.com/svn/trunk@13603 2bbb7eff-a529-9590-31e7-b0007b416f81
2014-02-26 23:01:57 +00:00
..
DM.cpp DM: also run benches once. 2014-02-26 23:01:57 +00:00
DMBenchTask.cpp DM: also run benches once. 2014-02-26 23:01:57 +00:00
DMBenchTask.h DM: also run benches once. 2014-02-26 23:01:57 +00:00
DMCpuTask.cpp DM: also run benches once. 2014-02-26 23:01:57 +00:00
DMCpuTask.h DM: also run benches once. 2014-02-26 23:01:57 +00:00
DMExpectations.h Add support for reading a directory of images with --expectations (-r). 2013-12-10 14:53:16 +00:00
DMExpectationsTask.cpp Add support for reading a directory of images with --expectations (-r). 2013-12-10 14:53:16 +00:00
DMExpectationsTask.h Add support for reading a directory of images with --expectations (-r). 2013-12-10 14:53:16 +00:00
DMGpuTask.cpp DM: also run benches once. 2014-02-26 23:01:57 +00:00
DMGpuTask.h DM: also run benches once. 2014-02-26 23:01:57 +00:00
DMPipeTask.cpp Change device factories to take SkImageInfo instead of SkBitmap::Config 2014-02-16 00:59:25 +00:00
DMPipeTask.h DM: add --pipe 2013-10-28 19:51:26 +00:00
DMReplayTask.cpp DM: don't run rtree when kSkipTiled is set. 2014-02-21 19:19:47 +00:00
DMReplayTask.h Reverting r12427 2013-12-02 13:50:38 +00:00
DMReporter.cpp Let DM run unit tests. 2014-02-26 16:31:22 +00:00
DMReporter.h Let DM run unit tests. 2014-02-26 16:31:22 +00:00
DMSerializeTask.cpp Change device factories to take SkImageInfo instead of SkBitmap::Config 2014-02-16 00:59:25 +00:00
DMSerializeTask.h DM: add --serialize 2013-10-21 18:40:25 +00:00
DMTask.cpp DM: also run benches once. 2014-02-26 23:01:57 +00:00
DMTask.h DM: also run benches once. 2014-02-26 23:01:57 +00:00
DMTaskRunner.cpp Let DM run unit tests. 2014-02-26 16:31:22 +00:00
DMTaskRunner.h Let DM run unit tests. 2014-02-26 16:31:22 +00:00
DMTestTask.cpp DM: also run benches once. 2014-02-26 23:01:57 +00:00
DMTestTask.h DM: also run benches once. 2014-02-26 23:01:57 +00:00
DMTileGridTask.cpp Change device factories to take SkImageInfo instead of SkBitmap::Config 2014-02-16 00:59:25 +00:00
DMTileGridTask.h DM: add --tileGrid 2013-11-26 23:36:51 +00:00
DMUtil.cpp DM: also run benches once. 2014-02-26 23:01:57 +00:00
DMUtil.h DM: also run benches once. 2014-02-26 23:01:57 +00:00
DMWriteTask.cpp add new copyTo version to SkBitmap, which takes SkColorType 2014-02-23 03:59:35 +00:00
DMWriteTask.h Add support for reading a directory of images with --expectations (-r). 2013-12-10 14:53:16 +00:00
README Reverting r12427 2013-12-02 13:50:38 +00:00

DM is like GM, but multithreaded.  It doesn't do everything GM does yet.

Current approximate list of missing features:
  --config pdf
  --mismatchPath
  --missingExpectationsPath
  --writePicturePath

  --deferred


DM's design is based around Tasks and a TaskRunner.

A Task represents an independent unit of work that might fail.  We make a task
for each GM/configuration pair we want to run.  Tasks can kick off new tasks
themselves.  For example, a CpuTask can kick off a ReplayTask to make sure
recording and playing back an SkPicture gives the same result as direct
rendering.

The TaskRunner runs all tasks on one of two threadpools, whose sizes are
configurable by --cpuThreads and --gpuThreads.  Ideally we'd run these on a
single threadpool but it can swamp the GPU if we shove too much work into it at
once.  --cpuThreads defaults to the number of cores on the machine.
--gpuThreads defaults to 1, but you may find 2 or 4 runs a little faster.

So the main flow of DM is:

    for each GM:
        for each configuration:
            kick off a new task
    < tasks run, maybe fail, and maybe kick off new tasks >
    wait for all tasks to finish
    report failures