Hi Gatling Team,
I am new to Gatling World. Currently we are using Jmeter tool in our open source list for the clients application. We have few questions:
- Using Jmeter we get a lot of resource issues. Do we have some advantage in Gatling?
- To test our client servers we require different IPs to hit the servers, like distributed testing in Jmeter using controller and load generators. How Does Gatling support this?
- We required to run approx 30K users tests, Using Jmeter it is reallly time cosuming and requires a lot of EC-2 machines. How does Gatling Help On this?
Thanks in advance
In terms of architecture, Gatling is asynchronous and message oriented, while JMeter is one-thread-per-user based.
So generally speaking, yes Gatling is more resource affective than JMeter: users are just messages, not threads (which cost memory and CPU). Gatling typically uses about 5 threads per core).
- If your resource problems are only the ones I described above, Gatling would be a good solution. Then, depending on your use case, you might require a lot of resources anyway. It depends on your use case: loading tons of heavy pages in memory and performing heavy processing come of course with a cost.
- We haven’t automated it yet, but you can scale out manually: https://github.com/excilys/gatling/wiki/Scaling-out
- 30K users/30K concurrent connections is not a problem with Gatling. The limits are NIC and bandwidth: you’ll probably have to go with m1.xlarge instances.
Thanks For your reply
there are many clients coming to us for executing 10K+ users load test. Currently we are using Jmeter, Just heared about gatling and wanted some initial evaluation of this product and how it can provide better results for performance tuning and to analyse the capacity of the system under test.
Is there any way that can convert Jmeter script to Gatling apart from Proxy settings something like GIT command/in built converter in gatling?