Measurement of response times for 22.1
All response times are measured after the browser are cached, and after the user logs on and runs through the use cases once. Measurements are timed on the second round of use cases but in the same session.
Fiddler tool is used to measure timings on a client computer with the following specifications:
- Model: VM
- OS: Microsoft Windows Server 2012 R2
- CPU: 8 processors (Intel Xeon 2.00 GHz, single core)
- RAM: 16 GB
- Web browser: Google Chrome 94
The following are the Chrome browser settings:
- Clear the Do not save encrypted pages to disk check box.
- Clear the Empty Temporary Internet Files folder when browser is closed check box.
- Disable all browser add-on toolbars and plug-ins except HTTPWatch.
- Configure the browser cache setting to Automatic.
- Configure the maximum browser cache size to 250 MB.
The SoftPerfect Connection emulator is installed and configured on a client computer to set high latency.
Definition of session types
There is concept of a First Session, a New Session, and an In Session with respect to the BMC Helix Innovation Suite Application logon session. The following table describes the types of Application's logon sessions:
Remedy Mid Tier logon session | Description |
|---|---|
First session |
|
New session |
For example, a support user logs on in the morning. |
In session |
For example, the remainder of the day after a support user logs on in the morning. |
Response times vary, depending on which session type is measured. In Session produces the fastest response time of the session types and First Session produces the slowest response times. In Session is the most commonly measured BMC Helix Innovation Suite Application's logon session type because it describes the typical work environment.