tree 63988f49b89bb07bacf83e41422eb8860fe43df3
parent 9f19a08fa3db6e3d9ddb8e7550b963a2a31e2c18
author Marco Miller <marco.miller@ericsson.com> 1591910192 -0400
committer Marco Miller <marco.miller@ericsson.com> 1591910192 -0400

CheckProjectStatisticsAfterGc: Make tests circular

Rename that scenario to CheckProjectStatisticsUpToGc and make it fully
circular. Make the scenario periodically check for garbage collection,
up to 10 seconds.

CheckProjectStatisticsUpToGc reports Gatling KOs for every check not
lending a done gc at the time of that period. Typically, the scenario
starts reporting Gatling OKs once garbage collection gets completely
executed. The OK/KO ratio may then be a measure of the jgit-based gc
performance within plugin's gc-executor component.

For example, the last local tests reported 5 KOs on average with
gc-executor's current 2.14 version (EOL), which runs jgit version
4.7.9.201904161809-r. Meaning, a gc that takes around 5 seconds to
complete for the hereby amended CreateChangesTriggeringGc scenario.

Increase the amount of "garbage" to collect in CreateChangesTriggeringGc
by multiplying changes up to over a thousand. Do so to increase gc times
thus making them easier to report about this way. Fix that scenario's
relativeRuntimeWeight, which was too high before and made this change
harder to realize.

Make the first changesPerSecond value letter lowercase as it becomes
calculated (a Scala convention).

Change-Id: I1af15c1294f54fff3a08efdd5c2fafa77be92b88