reduce the stress load on TypedCounter_test, to avoid testsuite out of memory
This commit is contained in:
parent
7bac890790
commit
d7ef67e821
1 changed files with 10 additions and 2 deletions
|
|
@ -71,11 +71,19 @@ namespace test{
|
|||
|
||||
namespace { // test data and helpers...
|
||||
|
||||
const uint MAX_FAMILIES = 20; ///< maximum separate "families", each sharing a TypedCounter
|
||||
const uint MAX_MEMBERS = 30; ///< maximum members per family (member == test thread)
|
||||
const uint MAX_FAMILIES = 5; ///< maximum separate "families", each sharing a TypedCounter
|
||||
const uint MAX_MEMBERS = 20; ///< maximum members per family (member == test thread)
|
||||
const uint MAX_ITERATIONS = 50; ///< maximum iterations within a single test thread
|
||||
const uint MAX_DELAY_ms = 3; ///< maximum delay between check iterations
|
||||
|
||||
/* Hint: number of threads = MEMBERS * FAMILIES
|
||||
*
|
||||
* The values set here are fairly conservative,
|
||||
* but increasing the number of threads causes the test suite
|
||||
* to fail frequently. Please increase these values e.g.
|
||||
* to 20 and 50 for a more thorough stress test!
|
||||
*/
|
||||
|
||||
|
||||
/**
|
||||
* Interface to a family of dummy types
|
||||
|
|
|
|||
Loading…
Reference in a new issue