First Performance Tests

For last testing we are heavy business transaction doing the following :
- HTTP Request1 : Request the inital page via HTTP GET request
- HTTP POST Request2: Uses a HTTP post request to
- Start a JTA transaction ( Not JTA transaction are always XA transactuons
- Run JPA flush [ == Insert a new db record ]
- Suspend the JTA transaction using the JEE TransactionManager API
- Add JTA transaction object, Entity Manager object to our HTTPSession Object
- HTTP POST Request3: Uses a HTTP post request to
- retrieve JTA transaction object and Entity Manager object from our HTTPSession Object
- Resume the Transaction and update the record
- Commit the record - in case of any errors rollback the transacton
- Cleanup HTTP session object , clear the Entity Manager
- HTTP Request4: Uses a HTTP post request to
- Invalidate the HTTP session
For performance testing we modify our Thread Group :
Number of Threads ( user ) : 5
Loop Count : 1000
This JMETER session will run 5.000 Business Transactions
Note: Disable all Listeners for Throughput / Performance Testing as listeners are very CPU and
Memory intensive .
-> For the inital performance test we will run only using the Summary reportFindings :
- We are running 5.000 Transactions with a throughtput of 200 HTTP request per second
- About 0.18 % of our HTTP requests are failing
- The average duration of our HTTP post are between 30 and 59 msAs we get some errors we will add the View Results Tree.
Because we are in a testing phase where we print errors and runtine information to the User
screen the HTML will give us an easy way to get details about the error

This website stores some user agent data. These data are used to provide a more personalized
experience and to track your whereabouts around our website in compliance with the European
General Data Protection Regulation. If you decide to opt-out of any future tracking, a cookie will be set up in your browser to remember this choice for one year. I Agree, Deny