Database Volume Testing

Last published posts

Mobile Application Testing: 10 Steps Approach
Posted on

Mobile application testing is crucial in order to create a reliable product. In this post, we’ll go over the entire testing process step-by-step. Testing is a crucial part of the mobile application lifecycle. However, due to all the time and effort, it takes to complete the full cycle of app testing, it gets overlooked by…
Read more…

Real Agile Approach to Performance Testing
Posted on

Performance testing helps to determine if a system is reliable and comfortable to use. In this post, we’ll explain the main principles of Agile performance testing as well as its benefits. Before launching an app or a website, it’s crucial for a developer and admin to know how the entire system behaves under stressful situations….
Read more…

Posted on

In the development and delivery of software, the most important contribution of DevOps is the elimination of the time lag between project phases: development, testing, trial operation, and delivery of the product to the final consumer. The time2market indicator is one of the key indicators of the competitiveness of products and the success of companies…
Read more…


Database volume testing is a type of testing where the system is tested based on large volumes of data.


Minimizing the risks related to performance degradation, possible breakdowns or failures under loads that are caused by increases of data in the database by promptly discovering performance problems in the system’s operability, localizing the “bottlenecks” and providing recommendations for their resolving during volume testing.


The report on volume testing includes:

  • Information about changes in the system performance with increased data volumes within the parameters of the IT system response speed: response times of user operations (under different loads) and server-loading resources (CPU, Memory, I/O)
  • Analysis of the “bottlenecks” in the system operation and recommendations for improvements to the architecture and infrastructure of the system

Scope of work

  1. Creation of load testing methods
    • Collection and analysis of production environment statistics
    • Coordination of the performance requirements
    • Determination of business processes and load scenarios
    • Determination of components for reliability testing
    • Description of the interactions with the external systems
    • Calculation of the intensity and determination of the load profiles
    • Description of the requirements for the DB volumes
    • Creation of a test plan
  2. Creation of a test model
    • Development of load scripts
    • Development of external system emulators
    • Creation of load scenarios
    • Creation of scripts for generation/depersonification of the database
    • Creation of data pulls
    • Guides for conducting the test
  3. Test preparation
    • Checking the operability of the test environment
    • Installing the testing tool on the load stations
    • Tuning the monitoring tools
    • Conducting trial tests
  4. Conducting trials
    • Launch tests for checking the system reliability in accordance with the load scenarios
    • Shutdown/restart of the chosen system components
    • Launch tests to check the fail-safety of the system
    • Results analysis
  5. System analysis
    • Analysis of the bottlenecks in the system performance
    • Analysis of the influence of a shutdown/restart of the chosen components on the business processes
    • Analysis of the system restoration time after a shutdown/restart of the chosen components
    • Preparation of the recommendations for changes in the system architecture and infrastructure or the development of relevant regulations

Service Limitations

This testing is not functional and is not intended to discover functional bugs. However, all discovered functional defects will be noted and presented to the customer.


Tools and licences

  • HP Load Runner
  • Apache JMeter
  • MS Visual Studio
  • IBM Rational Performance Tester
  • Silk Performer