The objective of load testing is to simulate realistic user activity on the application. If a non-representative user journey is used, or if the appropriate load policy is undefined, the behavior of the app under load will not be able to be properly validated.
Modeling performance tests doesn’t require a technical skill set, just the time to fully understand the ins and outs of the application:
- How users work on the system; their habits
- When/where/how often they’re using the application
- Is there any relation between external events and activity peaks?
- Is the company business plan related to application activity?
- Is the user community going to expand in different geographies?
- Is there a marketing plan focused on app promotion? If yes, who is the audience?
- Are there any layers of architecture shared with other systems?
To fully understand the application during performance modeling, the following roles should be involved:
- Functional architect
- Business analyst(s)
- Project leader
Of course, different functional roles will provide different feedback. The goal should be to understand the application, the end users’ habits, and the relation of the application to the current/future state of the organization.
System logs or database extractions can also be useful. These easily point out the main components and functional areas currently used in production. They also would retrieve the number of transactions/hour per business process.
- When considering the user load, it is important to be aware of the difference between the number of concurrent users and the number of users within the expected audience. An application delivered to 5,000 users may only have 500 users accessing it simultaneously.
- If there isn’t any estimation on the volume of maximum concurrent users, the number of users can be calculated based on the number of transactions/hour per business actions.
Establish Service Level Agreements (SLAs) & Service Level Objectives (SLOs)
Service Level Agreements and Service Level Objectives are the keys to automation and performance validation. The project leader and functional architect need to define ideal response times for the application. There are no “standard” response times.
SLAs/SLOs enable the performance engineer to provide status on performance testing results. With these, performance testing can be easily automated to identify performance regression between several releases of the application.
If the importance of component testing and performance testing in an early project stage is properly understood, the component-level SLA or SLO must be defined to enable successful automation.
Each test run will address one risk – and provide status on the performance requirements.
Most projects only focus on reaching an application’s limit. This is important to validate sizing and architecture configuration. However, it most likely will not answer all of the performance requirements.
There are other tests that need to run to properly to qualify app performance. These tests will help validate performance requirements:
- Unit test: Many projects overlook the power of unit testing. Don’t start running load tests if the performance is not acceptable with one single user. Unit testing allows the application to be instrumented with deep-dive analytics tools and provides useful information to the developers. This step should be a mandatory part of any load testing strategy.
- Connection test: Let’s say that each morning, all of the application users connect to the system at roughly the same time, then grab a coffee or chat with a colleague. Even if there are no major activities on the business components of the application, the architecture has to handle this peak user session scenario. It should be obvious to ensure that the system won’t break every time this happens. Lives will be much easier for the Ops team by validating this point. This test will ramp up all the expected users.
- Production activity test: Every application has major business actions. These actions often result in data being updated or inserted into the database. Therefore, there should be a good understanding of the number of records created per day/hour. Production activity testing ensures that the system can handle the load related to the number of transactions/hour expected in production. This test will load/validate the behavior of the business components within the database. Two main requirements for this type of test are the number of transactions/hour per user journey and appropriate think times.
- Peak test: Every application experiences peak volumes. Even if those peaks appear as infrequently as once or twice a year, it is mandatory to ensure that the application can handle them. Peak testing’s purpose is to simulate an important increase of users during a short period (e.g., a retail site’s simulation of activity resulting from typical holiday sales frenzy).
- Soak test: The application/architecture will most likely be available for several days or even weeks on end. In the absence of dedicated times set for maintenance tasks, it is important that the architecture will run without failure over a long period. Soak testing runs a constant number of users over extended time frames. With this test, it will be easy to identify any memory leak/network conjunction so that you can easily monitor the stability of the environment’s current configuration.
- Batch test: Some apps are designed with asynchronous tasks or batches. What is the impact of a batch on the real users? Batch testing will run the production activity and trigger the execution of a batch at a specific test moment. The purpose is to identify if the batch has any impact on the user experience.
Some other load tests could be utilized depending on the constraints of the business and the locations of the users. There are always events related to the company/organization that will affect the application load.
For example, the load designed for a trading application will depend on the opening hours of different markets. The app will have three typical phases: one for Asian users, a second for European users combined with additional Asian users, and the third for the U.S., which combines users from all three. Every time the markets open or close, there are peaks on trading activity. Therefore, testing would include different load types combining various business-case combinations.
On the other hand, there are also tests that are designed to validate the platform availability during maintenance tasks or a production incident:
- Failover test: The purpose of this test is to simulate a production failure on the environment. This type of test is mandatory to validate the availability of the environment and to make sure the failover cluster mechanism reacts properly. When the architecture has N nodes, it is important to validate that the N-1 or N-2 nodes can handle the expected load (to avoid event cascading during production issues). The Ops team is probably also interested in whether they can complete their maintenance tasks without having to set the app into a maintenance state. Most high-availability applications have many nodes on different layers of the architecture: web servers, application servers, database, etc. There should be one test per layer.
- Recovery test: The opposite of the degradation test, the recovery test is initiated by stopping one of the nodes and then restarting it while the app is loaded. Its purpose is to see how the node reacts to a heavy load post-restart.
Additionally, there may be operational situations to include during the load test to measure application behavior when the cache is being cleaned up.
There is yet another point that could affect the performance of the application: the data. Often when load testing, a test database with less data is used, or at least a database that has been anonymized for security purposes. The anonymous process usually creates records starting with the same letters/digits. So, all of the indexes used during the load test will be incomparable to those of the normal production database.
Data grows rapidly in production. Database behavior is quite different depending on the size of the database. If the lifetime of the database is long, then it might make sense to validate the performance of different sized databases to determine if there is the limit is different between a light and a heavy database. To achieve this, a large dataset pointing to various areas of the database should be used (e.g., never use a list of names where all the accounts start with AA or AAA2). Instead, keep a representative set of data from A to Z.
The type and complexity of the test will change during the project lifecycle:
Include think times
An important element of performance design, think time is the time needed by a real user between two business actions:
- Time to read information displayed on-screen
- Time to fill out information in a form
- Other real user actions that do not cause interaction with the application servers
Because every real-world user behaves differently, think times will always be different. Therefore, it is important:
- To gather the think time of each business step in each scenario. Avoid using the same think time for each step. There are always screens displaying information that end users need to read or forms they need to fill out before progressing to the next step. There should be a specific think time for each action.
- To calculate the average minimum think time and the average maximum think time/action.
- To let the load testing tool randomly choose a think time from a specified range (min and max).
Imagine the application is a castle with big walls and doors. Components that will be validated (via load testing) are inside the castle. The wall will represent proxy servers, load balancers, caching layers, firewalls, etc.
If a test is run without including think times, then only the main door would be hit. Okay, it may break, but there is a big chance that it would lock everything out after a short time. Be gentle and smart, and hide from the defense. The main door will allow entrance, and the components located inside of the castle will be able to be properly load tested.
Validate the user experience
As mentioned earlier, once the application is assembled, testing objectives will change. At some point, the quality of the user experience needs validation too.
Mobile applications, rich Internet applications (RIA), and complex AJAX frameworks are challenging in the way most are used to measure response times. In the past, measurements have been limited to download time and time to first byte (TTFB).
Measuring the user experience is possible by combining two solutions: load testing software (Tricentis NeoLoad) and a browser-based or mobile testing tool.
The load testing tool will generate 98% of the load on the application. The browser-based or mobile-based testing tool will generate the other 2% of the load to retrieve the real user experience (including the rendering time) while the application is loaded.
This means that the business processes and transactions to be monitored by the browser/mobile-based solutions need to be carefully identified.
Running tests without monitoring is like watching a horror movie on the radio. You will hear people scream without knowing why. Monitoring is the only way to get metrics related to the behavior of the architecture.
However, many projects tend to lack performance monitoring due to:
- The lack of tools
- The fear of the requirements needed to enable monitoring
Though monitoring is not limited to the operating system of the different server(s), its purpose is to validate that each layer of the architecture is available and stable. Architects took time to build the smartest architecture, so it is necessary to measure the behavior of the different layers.
Monitoring allows for a more comprehensive understanding of the architecture and the investigation into the behavior of the various pieces of the environment:
- Operating system: CPU, memory, disk, and network utilization
- Application server: memory utilization, garbage collector, thread utilization, sessions
- Web server: worker, number of sessions
- Database: buffer pool, cache utilization, number of transactions, number of commits, % indexed queries
- Caching server: hit ratio
Many projects use production monitoring tools to retrieve metrics from the architecture. This approach is not recommended since production monitoring has a large granularity between each data point (every 2-5 minutes). In load testing, it is important to have monitored data collected at least every five seconds. The performance engineer needs to be given every opportunity to identify bottlenecks. When a peak appears for only a few seconds during a test, it is vital to have enough granularity to point out the bottleneck.
Monitoring requires technical requirements such as a system account, which services to be started, firewall ports to be opened, etc. Even if it seems difficult to meet those requirements, monitoring is possible if there is proper communication with Operations; sending them these requirements in advance will facilitate that communication.
A key takeaway for monitoring: Anticipate requirements at an early stage.
This is the third article in a four-part series focused on practical guidance for modern performance testing:
Part 3 – Modeling performance tests
Part 4 – Executing performance tests
The post was originally published in January 2018 and was most recently updated in July 2021.