Explicitly state, that parallelism enhancing options are to be used in parallel performance tests, if it is best practice to use them on the respective versions. A prerequisite for those options is that using them does not require, even under heavy load but assuming enough capacity in the cluster, any jobs to be retried.
Signed-off-by: Klaus Aehlig <[email protected]> Reviewed-by: Hrvoje Ribicic <[email protected]> Cherry-picked from a305cb96e24303414ed4512932be8208fc5fdcca. Signed-off-by: Klaus Aehlig <[email protected]> --- doc/design-performance-tests.rst | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/doc/design-performance-tests.rst b/doc/design-performance-tests.rst index e3e2bf6..173289d 100644 --- a/doc/design-performance-tests.rst +++ b/doc/design-performance-tests.rst @@ -87,8 +87,12 @@ number of instances and parallel jobs can be tested realistically. The following tests are added to the QA: * Submitting twice as many instance creation request as there are - nodes in the cluster, using DRBD as disk template. As soon as a - creation job succeeds, submit a removal job for this instance. + nodes in the cluster, using DRBD as disk template. + The job parameters are chosen according to best practice for + parallel instance creation without running the risk of instance + creation failing for too many parallel creation attempts. + As soon as a creation job succeeds, submit a removal job for + this instance. * Submitting twice as many instance creation request as there are nodes in the cluster, using Plain as disk template. As soon as a creation job succeeds, submit a removal job for this instance. -- 2.0.0.526.g5318336
