anchor.diff:  ----
   
   If a 32 core machine, you should see periods during which 32 forked jvms appear in your process listing each running unit tests.
  -Your milage may vary. Dependent on hardware, overcommittment of CPU, memory, etc., can bring the test suite crashing down,
  -usually complaining of system exit and incomplete test report xml files. Start gently, with the default fork setting which
  -uses a quarter of the available CPUs.
  -
  -Adding the `--threads=N`, maven will run N modules in parallel when dependencies allow. Be aware, if you have
  -set the forkcount to `1.0C`, and the threads count to '2', the number of concurrent test runners can approach
  -2 * CPU count likely overcommitting the host machine.
  +Your milage may vary. Dependent on hardware, overcommittment of CPU and/or memory can bring the test suite crashing down,
  +usually complaining with a spew of test system exits and incomplete test report xml files. Start gently, with the default fork
  +and move up gradually.
  +
  +Adding the `--threads=N`, maven will run N maven modules in parallel (when module inter-dependencies allow). Be aware, if you have
  +set the forkcount to `1.0C`, and the `--threads` count to '2', the number of concurrent test runners can approach
  +2 * CPU, a count likely to overcommit the host machine (with attendant test exits failures).
   
   You will need ~2.2GB of memory per forked JVM plus the memory used by maven itself (3-4G).
   
  +===== RAM Disk
   
   To increase the speed, you can as well use a ramdisk. 2-3G should be sufficient. Be sure to
   delete the files between each test run. The typical way to configure a ramdisk on Linux is:
  
positive.code: 
  ----
  mvn test -PrunAllTests -Dtest.build.data.basedirectory=/ram2G
  ----
  
  On earlier versions, use:
  
  ----
  mvn test -P runAllTests -Dtest.build.data.basedirectory=/ram2G
  ----
  
  [[hbase.unittests.cmds.test.hbasetests]]
  
negative.code: 
  By default, `$ mvn test -P runAllTests` runs all tests using a quarter of the CPUs available on machine
  hosting the test run (see `surefire.firstPartForkCount` and `surefire.secondPartForkCount` in the top-level
  hbase `pom.xml` which default to 0.25C, or 1/4 of CPU count). Up these counts to get the build to run faster.
  You can also have hbase modules
  run their tests in parrallel when the dependency graph allows by passing `--threads=N` when you invoke
  maven, where `N` is the amount of parallelism wanted.
  maven, where `N` is the amount of _module_ parallelism wanted.
  
  For example, allowing that you want to use all cores on a machine to run tests,
  you could start up the maven test run with:
  