Performance audit and Remote Banking system load testing
Our client is a large national bank from the TOP-40 of the financial rating. The bank offers multi-faceted service packages to corporate, as well as to physical clients.
Got a project in mind?
There is no better place for a QA solution than Performance Lab.Drop us a line to find out what our team can do for you.
The bank has integrated the subsidiary banks In 2017-2020, following that the IT-landscape has grown and centralized. Remote Banking system allows each client to access the bank services through the Internet portal or the mobile application.
As a result of the integration the system has gained a significant amount of clients (the numbers have doubled), most of which possessed a salary bank card and other products.
As the new users have been gradually added to the Remote Banking system, there not only have appeared problems with its availability, but also the system crash frequency has risen. It has happened in the days of the peak user activity, such as payments and transactions in 2-3 days after the advance and salary payments.
The problem was not solved by adding additional server hardware, as the hardware utilization has by far not reached its peak – it was the system architecture that had to be improved.
The client has decided to involve the Performance Lab specialists in improving the Remote Banking performance and robustness.
The problem had to be solved as soon as possible. During the first phase we have performed a performance audit, monitoring the system state during the peak hours and days. Moreover, we have performed the load testing on production together with the bank support team at night, when the user load and the reputation risks are minimal.
Performance audit has allowed to detect and solve the most critical problems with the traffic volume and long query waiting time. It allowed to prevent system crashes in critical moments.
Of course, there are certain limits with testing on production. For instance, we had to be careful with the user data, as well plan our work according to the system availability. That’s why we have continued to improve the system performance on staging.
During the second phase we have collected and analyzed the user statistics from different sources. Then we have formed a combined load profile, developed a data emulator and performed several load testing iterations. Thanks to these activities, we have discovered about 20 performance issues with the DBO-Online system.
Advantages for the client
Owing to the implementation of the Performance Lab recommendations, the system performance has been upgraded by the factor of 3 to 5.
Likewise, the reputation risks due to the system crashes have been mitigated without any additional costs on the server hardware.
The internal evaluation of Remote Banking has risen from 2.6 to 4 points in half a year. Although it was not stated in the contract, we have shared the load testing competencies with the client. Due to that the customer specialists can evaluate the system performance changes for new releases, which mitigates the system unavailability in the future.