Sadece uygulamalarınızın değil database sorgularınızın da performansını ölçmek için JMeter kullanabilirsiniz. Güçlü bir teknik test ürünü olan JMeter ile hangi sorgunuzun daha sorunlu olduğunu bulalım. You can use JMeter not only for measuring your applications performance but also your database queries. With this powerfull technical test tool, you can discover which database queries takes most of the time.

1. Database Performance
Testing with JMeter
www.keytorc.com

2. Agenda
» Building a Database Performance Test Plan
» Running Test
» View Results

3. Building a Database Performance Test Plan

4. Creating Test Plan
Every Jmeter projects starts with a default Test Plan. All the items(test script,
timers, randomization elements, etc…) should be placed under this «Test Plan»
Items that we’ll use in this example are:
- Thread Group
- JDBC Connection Configuration
- JDBC Requests
- Constant Timer
- Random Order Controller
- Aggregate Graph

5. Thread Group
«Thread Group» defines our users load, their ramp-up period and how
many times test scripts will be run.
Example: 100 users will join test execution in 30seconds time interval and
they will execute their test cases 5 times.

6. JDBC Connection Configuration
JDBC Connection Configuration element define the connection parameter
to our database. This example demonstrate connection configuration to a
local MySql server having a sample database SAKILA.
Database URL
JDBC Driver class
Username
Password
are a MUST
Variable Name should be set in order to
relate all database related elements with
each other.

7. JDBC Request
JDBC Request are containers that represents our queries
4 queries are created.
They will execute different queries.
Those queries are child to the «Test Plan».

8. Constant Timer & Randomization
In order to simulate real user behaviour, delays must be added between
query execution. Randomization is also cruciale as there’s no definite
answer which query runs the most.
Queries must be child
item to the
randomization item
which is «Random
Order Controller».
Delay will always be
1000ms. There are
different «Timers» you
may try.

9. Listeners
For reporting purposes, «Listeners» must be added to our «Test Plan».
In this example, «View Results Tree» and «Aggregate Graph» are added in
order to visualize our queries’ performance.

10. Running Test

11. Running the Test
Play button runs our test plan and we observe the results in our listener
components.

12. View Test Results

13. View Test Result
«Aggregate Graph» gathers the response information for each request. It
collects request count, min, max, average, error rate, approximate
throughput.

14. View Test Result
Sampler Result Request Response Data
View Results Tree gives us more insight on each query run.

15. View Test Result
Graph Results gives a visual representation of data throughput
and other numeric statistics.

16. Thank you
info@keytorc.com
Keytorc
Keytorc Software Testing Services
www.keytorc.com