Using JMeter to perform Load-Testing on PowerServer's Web API
summary
Uses Apache JMeter to record and replay HTTP calls against PowerServer Web API using the Sales demo app, with a recording proxy on port 480 and JMeter’s CSV Data Set Config and random-variable generators to vary inputs. Simulates 200 threads with 10s ramp-up for reads and also CRUD scenarios, extracts session and transaction IDs via regex and promotes them to properties/variables. Encounters deadlocks, DB connection and license limits, applies a NOLOCK SQL change and license swap, verifies results, then reverts run mode to 0 for security.
AI-written summary · about
chapters (10)
- 0:00Introduction to JMeter
- 1:07Setting up JMeter environment
- 9:12Recording test scenarios
- 21:55Parameterizing test variables
- 39:02Simulating single user load
- 46:18Simulating CRUD operations
- 1:05:19Scaling to multiple users
- 1:17:30Handling concurrency limits
- 1:20:26Using synchronizing timers
- 1:20:46Cleanup and security
related talks
16mPerformance testing – under pressure!
36mJMeter + GitHub = Understandable performance of your application
45mPerformance Testing and Tuning of Web Applications
06mAzure Load Testing
47mLoad Testing You Always Wanted
44mOnce upon a load test in real time
33mRun the load down your mobile app
41mLeverage Your Load Tests With JMeter And Selenium Grid