|
density
C++11 library for paged memory management, function queues, heterogeneous queues and lifo memory management
|
|
density
C++11 library for paged memory management, function queues, heterogeneous queues and lifo memory management
|
The directory 'test' contains a test program that you can build with cmake. The directory 'bench' contains a benchmark program that you can build with cmake. On Windows you can also build both at once with Visual Studio 2017 using the solution test/vs2017/density_tests.sln.
The test program executes a number of test on all the data structures of the library. When doing massive multithread tests, it scales to the host machine spawning 3 threads for each logical cpu of the system.
The test program supports the following command-line parameters:
- rand_seed:<32-bit unsigned integer> - default is zero. Seed used to initialize the main random generator.
If it is zero the random generator is initialized with <code>std::ranom_device</code>. In multi-thread test
the random generator for the spawned threads is forked from the main one.
- exceptions:<0 or 1> - default is 1. If non-zero enables the testing of exceptional execution paths. This is
done using test allocators and test objects that throw an exception once in every point that may possibly
throw.
- spare_one_cpu:<0 or 1> - default is 1. If non-zero in multi-thread tests the second logical processor is not used.
- print_progress:<0 or 1> - default is 1. If non-zero shows a percentage of the progress during queue test
- test_allocators:<0 or 1> - default is 1. If non-zero enables special allocators that detect bugs in the memory
management. The tests with the normal allocators are executed in any case.
- queue_tests_cardinality:<size_t> - default is 2000. Number of elements to push in every queue tests. In multi-thread
tests this number is partitioned among all threads.
If the test program is built with the macro DENSITY_USER_DATA_STACK defined, the normal data stack is replaced with a test data stack that checks for bug in the memory management.
Example:
The benchmark program needs to read the source files from which it is compiled. It uses the macro __FILE__ to locate them, which generally has a path relative to the project file. So if you execute the program from another location, you have to provide a source directory.
The benchmark program supports the following command-line parameters:
-source:<string> - by default empty, max length = 4095. Path to prepend to the __FILE__ macro to access the source files.
1.8.11