You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to minimise potential noise while running Kibana/ES and load executor (Gatling) on the same machine, we can limit CPU number that load executor can use.
Setup might look like:
# Isolate the Gatling process to the first 2 cores (2 physical cores)
sudo cset set --set=/benchmark --cpu=0-1
sudo cset proc --exec /benchmark mvn gatling:test -q -Dgatling.simulationClass=${simulationPackage}.${simulationClass}
Cleanup should be executed in the end:
function tearDown() {
echo "Destroying cgroups"
sudo cset set --destroy /benchmark
echo "Setting CPU powersave governor"
for (( cpu=0; cpu<=${CORE_INDEX}; cpu++ ))
do
sudo cpufreq-set -c ${cpu} --min ${MIN_FREQ} --max ${MAX_FREQ} --governor=powersave
done
}
The text was updated successfully, but these errors were encountered:
In order to minimise potential noise while running Kibana/ES and load executor (Gatling) on the same machine, we can limit CPU number that load executor can use.
Setup might look like:
Cleanup should be executed in the end:
The text was updated successfully, but these errors were encountered: