diff --git a/src/main/docbkx/developer.xml b/src/main/docbkx/developer.xml index 5d625cf183a..baf91a6a916 100644 --- a/src/main/docbkx/developer.xml +++ b/src/main/docbkx/developer.xml @@ -1044,17 +1044,22 @@ public class TestHRegionInfo { Running tests faster By default, $ mvn test -P runAllTests runs 5 tests in parallel. It can be increased on a developer's machine. Allowing that you can have 2 tests - in parallel per core, and you need about 2Gb of memory per test (at the - extreme), if you have an 8 core, 24Gb box, you can have 16 tests in parallel. + in parallel per core, and you need about 2GB of memory per test (at the + extreme), if you have an 8 core, 24GB box, you can have 16 tests in parallel. but the memory available limits it to 12 (24/2), To run all tests with 12 tests in parallel, do this: mvn test -P runAllTests - -Dsurefire.secondPartThreadCount=12. To increase the speed, you - can as well use a ramdisk. You will need 2Gb of memory to run all tests. You - will also need to delete the files between two test run. The typical way to - configure a ramdisk on Linux is: + -Dsurefire.secondPartForkCount=12. If using a version earlier than + 2.0, do: mvn test -P runAllTests -Dsurefire.secondPartThreadCount=12 + . To increase the speed, you can as well use a ramdisk. You will need 2GB + of memory to run all tests. You will also need to delete the files between two + test run. The typical way to configure a ramdisk on Linux is: $ sudo mkdir /ram2G sudo mount -t tmpfs -o size=2048M tmpfs /ram2G - You can then use it to run all HBase tests with the command: + You can then use it to run all HBase tests on 2.0 with the command: + mvn test + -P runAllTests -Dsurefire.secondPartForkCount=12 + -Dtest.build.data.basedirectory=/ram2G + On earlier versions, use: mvn test -P runAllTests -Dsurefire.secondPartThreadCount=12 -Dtest.build.data.basedirectory=/ram2G