You are viewing the documentation for Blueriq 15. Documentation for other versions is available in our documentation directory.

1     Introduction

Starting with release 11.0 Blueriq decided to introduce a forms performance report. Triggered by the new external session storage development this report doesn't serve solely the purpose of offering performance information to clients that use Blueriq forms exclusively (without any additional components like dashboards, process engine etc) but also offers us the possibility to compare and assess the response times for the memory and external session implementations.

 

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.

 

 

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

 

Returning to the user load it is important to say that the 2 attached reports are depicting a run with 450 threads (for the memory run) and a run with 800 threads respectively (for the redis run). Both runs are holding the load for 1 hour. As for the results themselves they are interpreted in the same study measurement way as the other Blueriq performance tests namely with the help of Apdex. For more information about Apdex, please see 03 Apdex method.

2     Reference Application

 

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 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.

 

 

The performance script carries the user from logging in, to searching for available ATMs (this is the 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 out of the application. 

 

Application Flow

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

StepNameDescription
1LoginThe user logs in with a username and password.
2Start projectStart the application and display the Welcome screen
3Open ATMs section

Switch to the Find Local ATMs page

4Search ATMsCreates 500 instances using the AQ_CsvConnectivityService and an external CSV file, then switches to the Confirm ATMs Found page.
5Display Search ResultsOpens the Display ATMs page where the previously created instances are displayed in an AQ_InstanceList with page size 20.
6Go to the loan offers pageNavigates to the Loan Offers page.
7Apply for prime offerUpdates an instance through the ‘AQ_InstanceUpdate’ service and navigates to the Loan Form page.
8Open calculatorOpens the Borrowing Calculator page
9Fill in fields (1)

Fills in the available page fields. Other conditional fields are presented to the user because of this action.

10Fill in fields (2)Fills in the newly available page fields. New fields are displayed because of this action.
11Fill in fields (3)

Fills in the newly available fields on the page.

12CalculateUpdates 3 instances belonging to separate entities using the ‘AQ_InstanceUpdate’ service and displays the calculation results to the user.
13Go to first pageReturns to the Welcome page.
14Open the loan offers pageNavigates to the Loan Offers page.
15Apply for a fixed rateUpdates an instance through the ‘AQ_InstanceUpdate’ service and navigates to the Loan Form page
16Fill in fields (4)Fills in the available fields on the page. Some fields are refresh fields and have validations.
17Fill in fields (5)Fills in the available fields on the page. Some fields are refresh fields and have validations.
18Fill in fields (6)Fills in the available fields on the page. Some fields are refresh fields and have validations.
19Continue

Navigate to the Personal Information page

20Fill in personal formFill in all fields and navigate to the Document Upload page.
21Upload file

Upload a file to certify the user's identity. As the upload is successful an ‘AQ_FileDownload’ container is generated on the page.

22Download fileDownload the previously uploaded file.
23Submit requestNavigate to the Confirmation page.
24Go to the loan offers pageNavigate to the Loan Offers page.
25Log outThe user logs out.

 

Application Interface

 

ScreenContent
WelcomeThe welcome screen with 4 inline containers, 3 text items and 2 buttons.
Find Local ATMsA page with 2 inline containers, a text item and 2 buttons.
Confirm ATMs FoundA page with 2 inline containers, a text item and 2 buttons.
Display ATMsDisplays the nearby ATMs using an AQ_InstanceList with page size 20. Also contains 2 inline contains and 2 buttons.
Loan OffersThe page contains dozens of containers and text items, each of them having presentation or content styles assigned.
Borrowing CalculatorContains 7 inline containers, 10 fields and 2 buttons. 5 fields are refresh fields, additional fields become available depending on the values entered into the refresh fields, using inline containers with preconditions.
Loan FormContains 3 inline contains, 1 texxt item, 3 buttons and 8 fields. 3 fields are refresh fields with validations.
Personal InformationContains 2 inline containers, 2 buttons and 16 fields. 4 fields are refresh fields. 2 fields have preconditions and are shown or hidden based on the information entered in the refresh fields.
Document UploadContains 4 inline containers, 2 text items, 1 button, an AQ_File_Upload container and intially zero AQ_File_Download containers. When a file is uploaded, a new AQ_File_Download container is displayed, using a repeat expression.
ConfirmationContains a logout text item, a text item confirming the completion of the loan request and a button which leads back to the Loan Offers page.

 

3     Simulating application usage

The simulation which is executed on the application during the performance test scenario depends on two variables:

  • the user load that must be simulated on the system during the test
  • the total duration of the test execution

 

The user load is a constant number of users (threads), with a rampup time of 5 minutes. The user load is different based on the session store type being used:

  • memory session store: 450 users
  • redis session store: 800 users

 

After the 5 minute ramp-up, the load is sustained for one hour.

4     Test environment

For the performance tests a typical hardware configuration is used that consists of two separate servers for the Runtime and JMeter. The specification of the test environment is described in the test reports.

 

  • No labels