Great video. I had an issue recently with Jmeter where I was load testing my rest API hosted on the cloud. When I did a ramp up to 100 users my internet started going down. Does this have to do anything with the number of threads being generated from my laptop? Is the number of concurrent users limited by the laptop specs or the internet bandwidth?
basically for a fast performing end system or product, you need your APIs to perform at their best. For e.g.: in 1 of my customer their requirement was that the all APIs should have the LOAD TESTED at 300 QPS or RPS and latency should at Max 300millisecond. using Jmeter we can see if our APIs are performing at that level or not. if yes then all good :) if not, check the server configuration, your REST Backend configurations, any resource intensive operations in Code etc. Then post the fix try again.
![Veeze - F.A.F (ft. Rylo Rodriguez) [Official Music Video]](http://i.ytimg.com/vi/7hlz2S2GmIY/mqdefault.jpg)
A brilliant tutorial on Jmeter..thanks for your help. You saved my research time... :thumbsup
Great video. I had an issue recently with Jmeter where I was load testing my rest API hosted on the cloud. When I did a ramp up to 100 users my internet started going down. Does this have to do anything with the number of threads being generated from my laptop? Is the number of concurrent users limited by the laptop specs or the internet bandwidth?
hi
how you are passing test data?
How to load test Python API with jmeter ?? parameter file path
Hit a api how to slove response time below 1 sec
Can you explain for beginners ..
learn and master webserver ,REST , API
basically for a fast performing end system or product, you need your APIs to perform at their best.
For e.g.: in 1 of my customer their requirement was that the all APIs should have the LOAD TESTED at 300 QPS or RPS and latency should at Max 300millisecond.
using Jmeter we can see if our APIs are performing at that level or not.
if yes then all good :) if not, check the server configuration, your REST Backend configurations, any resource intensive operations in Code etc. Then post the fix try again.