Database Performance Testing

Written by Kimberly Clark
Bookmark and Share

Database performance testing is done to identify weaknesses in the system and to see how well it functions when operating under maximum load. Whether or not the system can handle large quantities of data in a short amount of time or if it can perform several transactions during peak production periods are examples of metrics that could be tested. In any case, the system's performance is generally measured in terms of throughput rates and response time.

The term throughput describes the overall ability of the database to process data in a given period of time. When performing database performance testing, it is important to measure the throughput of the system under various operating conditions. This could include periods when several people are accessing the system at once or a busy processing time when a lot of data is being manipulated.

Examine Hardware and Software Options

When gauging the performance of the database, it is equally important to evaluate all associated hardware and software products. For instance, it might be necessary to determine if there are any measurable differences when the database is run on a desktop as opposed to a laptop. In addition, the performance of the database on or LAN (local area network) versus a WAN (wide area network) should be checked out.

Other things to look at are the network cards, I/O (input output) devices, and cache settings. Furthermore, before releasing the application into a production environment the tester should also examine how the database reacts to heavy user access and network traffic. Database performance testing should also involve looking into how the database behaves when used with different operating systems.

Bookmark and Share