Issues with Longevity Test

Gatling (Open-Source)
1

*** Using Gatling 2.1.4 on Ubuntu 14.10

I ran into an issue last night while running a 12 hour longevity test. The good news is the gatling simulation I ran found an issue with our docker container configuration and after running for a few hours under a moderate load it was running out of memory.

The bad news is I am not able to view the reports because the system I ran the test on ran out of disk space. The system I run my tests on is beefy HP Z-620 - 16GB memory, 1TB HDD, etc. When I ran my tests I started it like this:

nohup mvn gatling:execute -Dgatling.simulationClass=com.cliqueintelligence.qa.performance.test.simulations.contexts.CreateTaskForDurationSimulation -DatOnceUsers=100 -Denvironment=wareft1 &

The problem is that nohup.out grew to almost 900GB and I ran out of disk space and the test never finished. My questions are:

  1. Is this the best way to run a test like this?
  2. Is there a way to not output anything to console so nothing gets written to nohup.out? I know I can do this through Linux commands but wasn’t sure if there was a way in Gatling to not output anything to the console
  3. If I don’t output anything to the console is there a way to view the progress of the test while it’s running? Normally I would just tail -f nohup.out to see how things are going
  4. I now have a 65G simulation.log file sitting there. Is there a way to process that log file now so I can see a report of the transactions that did go through before I ran out of space?

Thanks,
Steve

2

Hi Steven,

3

If I don’t output anything to the console is there a way to view the progress of the test while it’s running?

docker run -d -p 8081:8081 --name grafana aidylewis/grafana
docker run -d \
           -p 8083:8083 -p 8084:8084 -p 8086:8086 -p 2003:2003 \
           -e PRE_CREATE_DB="gatling;grafana" --name influxdb davey/influxdb:latest