As part of the load and performance tests carried out by ArgumentIT, your system is tested using various load test scenarios.
A distinction is made between the following scenarios:
Continuous load test
This test is carried out over a period of 48 hours. During this time, a constant load is applied that corresponds approximately to the load in production. The aim of this test is to check whether all resources used by the application under test are released over a longer period of time. Allocated memory should always be released and not increase. In concrete terms, the application is checked for memory holes, for example. The response times of the application should therefore remain the same over a longer period of time.
Overload test
In this test, an increasing load is applied that grows beyond the load limits of the application to be tested. A drop in the availability of the application is accepted and even expected. When the load is reduced, it is checked whether the application recovers and continues to work normally. The aim of such a test is to find out where the current performance limit of the application is. An overload protection is also tested, which should be built into every system to be tested.
Peak load test
As the name suggests, a load is applied that approaches the peak performance of the application under test. However, the load is increased from zero to the peak load in a ramp-up phase. Such tests are carried out at regular intervals so that they can be compared. For applications under test, it can be checked whether newly installed modules may have a negative effect on the load behaviour.
Scaling test
Some applications scale. This means that when usage is low, few servers are used and the company also incurs lower costs. With higher usage, servers are added. The correct addition or deactivation of servers is checked by means of such a scaling test.