Breaking Point.

How to determine the breaking point of my application when performance testing from Gatling?

  • How can I best determine the breaking point of my application? (i.e. the point at which it becomes unresponsive)
  • Which listener will best be able to tell me the breaking point of my application (i.e. how many concurrent users it can handle)

Secure Link Services Group
Zürich: Innovation Center, Haldenstrasse 23, 8306 Brüttisellen, Switzerland
Dubai: Building 3, 3rd Floor, Dubai Design District, Dubai, United Arab Emirates
Dhaka: Midas Center, Road 16 (new), Dhanmondi, Dhaka 1209, Bangladesh
Thimphu: Bhutan Innovation Tech Center, Babesa, P.O. Box 633, Thimphu, Bhutan
Contact us: CH +41 (0)448058044 | US +1 213 260 1291 | www.selise.ch

Important Note: This e-mail and any attachment are confidential and may contain trade secrets and may well also be legally privileged or otherwise protected from disclosure. If you have received it in error, you are on notice of its status. Please notify us immediately by reply e-mail and then delete this e-mail and any attachment from your system. If you are not the intended recipient please understand that you must not copy this e-mail or any attachment or disclose the contents to any other person. Thank you for your cooperation.

I think you can try with this scenario setup where we increase users at each stage → https://gatling.io/docs/current/general/simulation_setup/#meta-dsl
by doing this, we can analyze the server metrics at each stage and find out its breaking point.
If server doesnt break at the first attempt, then we can increase users at each level in the next attempt and find out.

If you are planning on distributed testing with Gatling OpenSource, I think its not possible to get combined Real Time Monitoring stats (you would have to merge the log files at end of test and find out)
Gatling Frontline can offer a real time stats with distributed testing

Thank you.
I am using OpenSource Gatling.
So how to merge the log file? Will you help me to drop me a link on the merging things or any?

I think you can try with this scenario setup where we increase users at each stage → https://gatling.io/docs/current/general/simulation_setup/#meta-dsl
by doing this, we can analyze the server metrics at each stage and find out its breaking point.
If server doesnt break at the first attempt, then we can increase users at each level in the next attempt and find out.

If you are planning on distributed testing with Gatling OpenSource, I think its not possible to get combined Real Time Monitoring stats (you would have to merge the log files at end of test and find out)
Gatling Frontline can offer a real time stats with distributed testing

How to determine the breaking point of my application when performance testing from Gatling?

  • How can I best determine the breaking point of my application? (i.e. the point at which it becomes unresponsive)
  • Which listener will best be able to tell me the breaking point of my application (i.e. how many concurrent users it can handle)

Secure Link Services Group
Zürich: Innovation Center, Haldenstrasse 23, 8306 Brüttisellen, Switzerland
Dubai: Building 3, 3rd Floor, Dubai Design District, Dubai, United Arab Emirates
Dhaka: Midas Center, Road 16 (new), Dhanmondi, Dhaka 1209, Bangladesh
Thimphu: Bhutan Innovation Tech Center, Babesa, P.O. Box 633, Thimphu, Bhutan
Contact us: CH +41 (0)448058044 | US +1 213 260 1291 | www.selise.ch

Important Note: This e-mail and any attachment are confidential and may contain trade secrets and may well also be legally privileged or otherwise protected from disclosure. If you have received it in error, you are on notice of its status. Please notify us immediately by reply e-mail and then delete this e-mail and any attachment from your system. If you are not the intended recipient please understand that you must not copy this e-mail or any attachment or disclose the contents to any other person. Thank you for your cooperation.

Secure Link Services Group
Zürich: Innovation Center, Haldenstrasse 23, 8306 Brüttisellen, Switzerland
Dubai: Building 3, 3rd Floor, Dubai Design District, Dubai, United Arab Emirates
Dhaka: Midas Center, Road 16 (new), Dhanmondi, Dhaka 1209, Bangladesh
Thimphu: Bhutan Innovation Tech Center, Babesa, P.O. Box 633, Thimphu, Bhutan
Contact us: CH +41 (0)448058044 | US +1 213 260 1291 | www.selise.ch

Important Note: This e-mail and any attachment are confidential and may contain trade secrets and may well also be legally privileged or otherwise protected from disclosure. If you have received it in error, you are on notice of its status. Please notify us immediately by reply e-mail and then delete this e-mail and any attachment from your system. If you are not the intended recipient please understand that you must not copy this e-mail or any attachment or disclose the contents to any other person. Thank you for your cooperation.

You would need to place the log files in a single directory and run the command → https://gatling.io/docs/current/general/configuration/#zip-bundle-command-line-options

.\gatling.bat -ro

For maven → pls check the configuration https://gatling.io/docs/current/extensions/maven_plugin/#configuration

Real Time monitoring-> https://gatling.io/docs/current/realtime_monitoring/#graphite-influxdb-grafana