Agreed with Adrain. We too did POC of gatling but considering the points mentioned by Adrian ( scripting in scala when the scenarios get more complex) , We moved to Jmeter.
Thanks, Prateek On Tue, Feb 4, 2020 at 2:22 PM Adrian Speteanu <[email protected]> wrote: > Hi, > > While I'm not necessarily happy with the methodology used for comparison, > the point remains that there aren't significant differences when it comes > to the technical capabilities. So, in the end, it should come down to the > implementation team's preferences. Are they going to feel more comfortable > scripting in scala when the scenarios get more complex? Or do they prefer > using the GUI of JMeter? > > Implementing scenarios would be simpler in JMeter in my view, but it would > be easier to maintain scripts over time if they were coded (in any > language). > > -A > > > > On Tue, Feb 4, 2020 at 7:14 AM Soumya Nayak <[email protected]> wrote: > > > Hi Team, > > > > I came across a link about Gatling Vs JMeter . > > > > https://dzone.com/articles/gatling-vs-jmeter > > > > From the above link I could see some of the advantages of Gatling over > > JMeter with respect to memory and CPU usage. > > > > So anybody having more details can help me out this to create a line of > > difference to plan for the specific tool usage better. > > > > Regards, > > Soumya > > > > > > > > > ****************************************************************************************** > > This message may contain confidential or proprietary information intended > > only for the use of the > > addressee(s) named above or may contain information that is legally > > privileged. If you are > > not the intended addressee, or the person responsible for delivering it > to > > the intended addressee, > > you are hereby notified that reading, disseminating, distributing or > > copying this message is strictly > > prohibited. If you have received this message by mistake, please > > immediately notify us by > > replying to the message and delete the original message and any copies > > immediately thereafter. > > > > If you received this email as a commercial message and would like to opt > > out of future commercial > > messages, please let us know and we will remove you from our distribution > > list. > > > > Thank you.~ > > > > > ****************************************************************************************** > > FAFLD > > > -- ::DISCLAIMER:: ---------------------------------------------------------------------------------------------------------------------------------------------------- This message is intended only for the use of the addressee and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify us immediately by return e-mail and delete this e-mail and all attachments from your system.
