...

Because generally forms tend to be lighter on the memory consumption than other components it was decided to simulate a higher user load. This method assures that the differences in response times are clearer and less circumstantial and helps us draw some conclusions on the use limitations in a certain given environment with some certain given settings. In this way we learned for instance that the Runtime is slightly faster with an inmemory session keeping but on the other hand it supports a lower amount of users.

Image Modified

See 11. Performance Tuning for a more in-depth analysis of Memory vs. Redis session store performance and performance tuning advice.

...

In order for us to obtain relevant test results we needed to have a Blueriq application very much similar to a real application in production. Thus we aimed at having as much elements as possible (required fields, conditional fields, field validations, file upload/download containers etc) but also a reasonable profile size. The application poses as reference application used for forms performance testing is a bank website where the user can either search and find the available ATMs in his area or apply for one of the three available loans.

Image Modified

The performance script carries the user from logging in, to searching for available ATMs (this is the moment step where 500 instances are created - each of them containing 5 attributes), applying for a loan, filling fields, switching pages, uploading and downloading files and eventually logging back out of the application. It is this script that helped us in finding and resolving some forms performance issues and also in better understanding Blueriq performance in general.

...

Application Flow

The permance script consists of the following steps in the main application flow:

3     Simulating application usage

...