Additional Settings

In additional settings we have the following heading:

  • Logs & Reports
  • Pass/Fail Criteria using Check Profile Rules
  • Report
  • Percentile Data
  • Event Log
  • Advanced Settings
  • Transactions
  • HTTP(s)
  • SSL
  • Sync Points
  • Java Settings for Java Type Script
  • Health Check Settings
  • Netdiagnostic Settings
  • Network Simulation
  • User Profile
  • Profile
  • Location
  • Access
  • Browser
  • Screen Size
  • Global Directory
  • Advanced

Let us discuss on the above in details.

 

 

Logs and Reports

Pass/Fail Criteria Using Check Profile Rules

Every load test should have a pass/fail status. This can be easily done using check profile rules. Rules can be evaluated periodically while the test is running to get the real-time status of the test. You can use this to stop the test from failing to avoid time and resource wastage.

For overall test status, rules can be evaluated at the end of the test. Detailed pass/fail report highlights metrics as green, yellow, or red for quick root cause analysis.

In this, we have the following two ways to evaluate:

  • Evaluate Pass/Fail status periodically while test is running.
  • Run rules for overall Pass/Fail criteria.

To setup logs and reports, click the Additional Settings  in Scenario Page  as shown in below figure.

Figure 161 Additional Settings

On the additional settings page, click on Logs and Reports and select Pass/Fail Criteria Using Check Profile Rules as shown in below figure.

Figure 162: Pass/Fail Criteria using Check Profile Rules

Evaluate Pass/Fail status periodically while test is running

Rules should be run by keeping in mind the following conditions:

  • Window: Select whether the window should be fixed or moving.
  • Time: Choose the time in minutes.

Once conditions are applied then select the profile from the drop-down if any are available or from the local directory.

Once all the above conditions are selected, the following details are available:

  • Profile Name: It shows the profile name.
  • Profile Description: Describe the profile selected.
  • Check Rules: This column checks the rules applied to the profile.
  • Last Updated: It is the time when the profile was last updated.
  • Updated by: Shows the name of the person or team updated on the profile.
  • Action: It is used to edit or delete the profile selected.

Note: You can also check the given box if you want to skip the Ramp up, Stabilize and Ramp down phases. It will show Simple Scenario-based scheduling only.

Pass/Fail Criteria

  • Metrics used in rules are:
  • Green if SLA is upto 20%
  • Yellow if SLA is 21% – 50%
  • Red, if SLA is more than 50%
Figure 163: Pass/Fail Criteria
  • You can also check the box available if you want to stop the test in case of failure.
  • You can check the box, if you want to generate a report in case of:
  • All cases
  • Failure Cases

Run Rules for overall Pass/Fail criteria

To apply the same CheckRules as the periodic case check the available box.

Once the above conditions are applied then select the profile from the drop-down if any are available or from the local directory.

Once all the above conditions are selected, the following details are available:

  • Profile Name: It shows the profile name.
  • Profile Description: Describe the profile selected.
  • Check Rules: This column checks the rules applied to the profile.
  • Last Updated: It is the time when the profile was last updated.
  • Updated by: Shows the name of the person or team updated on the profile.
  • Action: It is used to edit or delete the profile selected.
  • Show metrics of baseline testruns in the pass/fail report.

In this, you can select the scenario and the test run in the respective baseline.

Note: You can also override the check profile SLA by selecting the check box available with the respective baseline by choosing them from the dropdown.

Pass/Fail Criteria

  • Metrics used in rules are:
  • Green if SLA is upto 20%
  • Yellow if SLA is 21% – 50%
  • Red, if SLA is more than 50%

NOTES

  • You can also check the given box if you want to skip the Ramp up, Stabilize and Ramp down phases. It will show Simple Scenario-based Scheduling only.
  • You can also override the check profile SLA by selecting the check box available with the respective baseline by choosing them from the dropdown.

Reports

To setup Logs and Reports, click the Additional Settings  in Scenario Reports as shown in Figure 116. On the additional settings page, click on Logs and Reports and select Reports as shown in below figure.

Figure 164: Reports
  • Generate virtual user trace log: It is used to trace the virtual users to look for errors that occur with certain virtual users and not with others.  If applied to a group, this can trace a particular virtual user accessing a particular page. Generate virtual user tracing by selecting this check box.
  • Auto-Generate Stats Report
Figure 120: Auto Generate Stats Report

When enabled, a stats report is auto-generated with the following information:

  • Report Type: Select the type of report required- Tabular, HTML or Word from the drop-down.
  • Template: It shows the list of available templates (having graph information).
  • Report Name: Enter the report name in this field.
  • X-Axis Time Format: Select the time format for X-Axis either ‘Elapsed’ or ‘Absolute’.
  • Time: It is the time selection for generating compare report:
  • Total Run
  • Run Phase only
  • Specified Time Interval
  • Generate NetCloud Compare Report after completion of the test
Figure 165: Generate NetCloud Compare Report

      When enabled, the following fields is get enabled:

  • Template Name: Select the template name from the list of available templates.
  • Report Set Name: Enter the presentable name of the report set.

Note: If you want to include the controller name, you can select the available check box with the report set name.

  • Time: Time selection for generating compare report:
  • Total Run
  • Phases
  • Specified Time Interval
  • Send test completion report at the end of the test: When enabled, a stats report is emailed to specified recipients after test completion with the following information:
  • TR number
  • Machine and Controller
  • Scenario
  • Start time of TestRun
  • Duration of TestRun
  • Send Report as an attachment: When enabled, a summary report is emailed to specified recipients after the completion of the test as an attachment.
Figure 166: Send test completion report at end of test

The attachment has the following information:

  • TR number
  • Machine and Controller
  • Scenario
  • Start time of TestRun
  • Duration of TestRun

Note: For multiple emails use comma separator.

Percentile Data

Percentile data provides insight into the distribution of metrics values. A percentile is the value of a variable below which a certain percent of observations fall. Therefore, the 20th percentile is the value (or score) below which 20 percent of the observations are found. This setting is used to have the graphical representation of the percentile report in the UI analysis window.  The user needs to select the Generate Percentile Data check box and specify the duration after which the percentile data is to be generated.

To setup Logs and Reports, click the Additional Settings  in Scenario Reports as shown in Figure 116. On the additional settings page, click on Logs and Reports and select Percentile as shown in below figure.

Figure 167: Percentile Data

The time interval can be any of the following:

  • 10 seconds
  • 1 minute
  • 10 minutes

Event Log

Event log is a log of occurrence or happening of a particular task or program, such as the completion of an asynchronous input/output operation. A task may wait for an event or any of a set of events or it may (request to) receive asynchronous notification that the event has occurred.

To access Event Log, click the Additional Settings  in Scenario Reports as shown in Figure 116. On the additional settings page, click on Logs and Reports and select Event Log as shown in below figure.

Figure 168: Event Log

To enable the event log, select the Enable Event check box. You have the following option in the Event log:

  • Event Log Levels: This specifies which level of events are to be logged. There are 5 levels- Information, warning, minor, major, and critical. Events are further filtered using the filter level before logging into the event log file.
  • Filter Criteria: This is used to filter out events based on two criteria. First is ‘Do not filter’ (in this case, events are not filtered) and the second is ‘Filter based on the events as per event definition file’ (in this case, filters on events are applied based on the event definition file).
  • Use Log Manager for all events and to save data API: Enable Log manager to starts LOAD TEST logging manager process. Each process sends events to the log manager by using TCP/IP.
  • Use System Assigned Manager Port: When enabled, the system assigned port is used, else the user needs to specify a port.

Advanced Settings

To access Advanced Settings, click the Additional Settings  in Scenario Reports as shown in Figure 116. On the additional settings page, click on Logs and Reports and select Advanced Settings as shown in below figure.

Figure 169: Advanced Settings

We have the following options in the Advanced settings of Logs and Reports:

  • Sample Interval: It is the time interval in which the logs and reports are refreshed. By default, the interval is selected as Auto. 10 secs is selected for the load test scenario in standalone mode (no generators) else it is 1 min.
  • Enable Scenario group-based test metric(s): When enabled, the dashboard displays Test metrics data based on specific groups of the Scenario.
  • Enable Page Based Stats: When enabled, Real Browser User (RBU) page stats metrics are displayed on the dashboard.
  • Enable Server IP address-based metrics: It helps to get the resolved IPs at run time in web-dashboard from which the request is being served (Sent/Sec).
  • Enable save nvm file param value: When enabled, save nvm file value is displayed.

 

 

Transactions

Here user can perform transaction-related settings. There are two sub-sections under this:

  • Pages as Transaction
  • Advance Transaction

To access Transaction, click the Additional Settings  in Scenario Reports as shown in Figure 116. On the additional settings page, select Transactions as shown in below figure.

Figure 170: Transactions

Pages as Transactions

Figure 171: Pages as Transactions

This option is used to enable or disable the transaction. It contains the following options:

  • Do not consider page as transaction: No transactions are created automatically for any page. However, users can create custom transactions within the scripts.
  • Consider each page as a transaction: The transactions are automatically created for each page. For example: For the Home page, a transaction named “tx_Home” will be created.
  • Consider each page’s success or failure as distinct transactions: Each page’s success or failure is considered as a transaction.
  • Consider each page status as different transaction: In this status of each page is considered as a distinct transaction for that page.

For example: For page status Home_Success, HomeConFail, and findflight_PartialHdr, transaction names will be “tx_success” and “tx_failuretype” where the failure type is ConFail and PartialHeader.

  • Do not add the ‘tx_’ prefix in the transaction name: ‘tx_’ is not prefixed with the transaction names. This option is available in all cases except ‘do not consider the page as a transaction scenario.

 

Advance Transaction

This sub-section contains some advanced settings for transactions.

  • Enable transaction cumulative metrics: The transaction cumulative graphs are added to the test metrics and the user can plot them onto the dashboard. The most common metrics are – Requests Completed & Requests successful in HTTP requests metrics.
  • Enable transaction grouping in transaction detail: To enable transaction grouping in transaction details, select the transaction group from the drop-down list.
  • Once all the above fields are filled, click the Save Changes icon at the top right corner of the page.

HTTP

To access HTTP, click the Additional Settings  in Scenario Reports as shown in Figure 116. On the additional settings page, select HTTP as shown in below figure.

Figure 172: HTTP(s)

There are two sub-sections within this

  • URL Encoding
  • Advanced

URL Encoding

Figure 173: URL Encoding

URL encoding is a mechanism of encoding information in a URI.

  • Encode space in URL and query parameters of URL: The user can specify how the space can be encoded in the URL and query parameter of URL. It has value + or %20 (from drop- down list).
  • Additional characters to be encoded in URL: It is the value or characters which the user wants to encode in a URL other than space.e.g. {,}, |, % etc.
  • Additional characters to be encoded in query parameters of URL: It is the value same or different characters which the user wants to encode in the query parameter.e.g. {.}, |, % etc.

 

HTTP Advance

Figure 174: HTTP Advance
  • Select cookie(s) with: Cookies received in the HTTP response are stored and used in the next HTTP request.
  • Attribute: Selecting “ignored” ignores the expiry of the cookie. Selecting “in the past then delete” deletes the cookie whose life span has expired already.
  • Redirection depth: Based on the location header that was received in the HTTP response, redirection up to a specific depth is permitted for any url.
  • Use parent URL method for redirected URL: Parent method (GET/POST) is used in the redirected URL request, else GET method is used.
  • Once all the above fields are filled, click the Save Changes icon at the top right corner of the page.

SSL

Secure Sockets Layer (SSL) is the standard security technology for establishing an encrypted link between a web server and a browser. To access SSL, click the Additional Settings  in Scenario Reports as shown in Figure 116. On the additional settings page, select SSL as shown in below figure.

Figure 175: SSL

SSL Option

Override SSL version for specified hosts: By default, SSL/TLS version is assigned for all hosts from the field given above. It overrides the existing default SSL version with the selected SSL version for specified hosts.

SSL Options

  • Recorded Host Name: It is the hostname of the recorded script. In case there is no recorded hostname then the host/IP is to be mentioned.
  • SSL Version: Select the required SSL/TLS version from the drop-down list which you want to apply on the above hostname.

Sync Point

Sync points mean ‘meeting points’. A Sync point creates an intense user load on the server at a time to measure server performance under load. It helps to see how a particular transaction of an application responds with loads. For example, to test a bank server, the user could create a scenario that contains two Sync points as ‘Deposit’ and ‘Withdraw’. The first Sync point ensures that 1000 Vusers simultaneously deposit cash. The second Sync point ensures that another 1000 Vusers simultaneously withdraw cash. To measure how the server performs when only 500 Vusers deposit cash, the user can deactivate the withdraw Sync point, and instruct 500 Vusers to participate in the deposit Sync point only.

To access Sync Point, click the Additional Settings  in Scenario Reports as shown in Figure 116. On the additional settings page, select Sync Point as shown in below figure.

Figure 176: Sync Points

Sync Points Option

  • Overall timeout for releasing sync point since first Vuser arrived at sync point (OATO)

Specify the maximum timeout for running a Sync Point. It determines the maximum wait time (in seconds) for each Sync Point to come to the release state from the time when the first VUser reached the Sync Point.

  • Maximum time allowed between two VUser to arrive at sync point (IATO)

Specify the maximum time between two VUsers arriving at SyncPoint. It determines the maximum wait time (in seconds) for each VUser to arrive at a Sync Point. After each VUser arrives at the Sync Point, it waits up to timeout for the next VUser to arrive.

Add Sync Point Option

Sync Point Settings
  • Enable SyncPoint at the start of the test: This field enables syncpoint at the start of a test.
  • Scenario Group: Name of the group where the Sync point is defined. It can be ALL or any user defined group name.
  • Vuser enter SyncPoint on start of: This field specifies the type of Sync point you want to create. It consists of the following options:
    • Page: Vuser enters the Sync point when the specified page starts.
    • Transaction: Vuser enters the Sync point when the specified transaction starts.
    • Script: Vuser enters the Sync point when the specified script starts.
    • API: The user can add a Sync point via custom API.

Syntax: ns_sync_point (Sync Point name);

Example: ns_sync_point (“Sync Point”);

You can also select a transaction, Page, Script, or Sync point API.

  • Participating Vusers %: Percentage of Vusers participated for a specific Sync point. This percentage is calculated over the total number of Vusers in case of ALL groups.
  • Release SyncPoint when: Specifies the number of Vusers that should reach a Sync point for releasing that Sync point.
Figure 177: Add Sync Point( Sync Point Settings)
Advanced Settings
Figure 178: Advanced Settings( Sync Point)
  • Do not release SyncPoint automatically: Enables you to release the sync point automatically or manually:
    • Manual release: If you select the Do not release SyncPoint automatically option, the Sync point is released forcefully from the Sync point window as per the requirements
    • Auto release: If you deselect the Do not release SyncPoint automatically option, the Sync point is released automatically based on the release type and release schedule.
  • Release SyncPoint: Specifies how the VUsers will be released.
    • At Target VUsers: If the target VUsers (as mentioned in the ‘Release Target VUsers’ field) reached, the Sync point is released.
    • At Absolute Time: Define the absolute date (in mm/dd/yyyy format) and time (in hh: mm: ss format) at which the VUsers needs to be released. The absolute date and time should be greater than the current date and time
    • After duration: Provide the period (in HH:MM: SS format starting from the time as soon as first VUser reached to the Sync point).
  • Release SyncPoint Vusers: Defines when the VUsers are released after they have reached their respective Sync point. The following options are available:
    • Immediate: Immediate release ofall the VUsers that reach Sync point.
    • Duration: Releases VUsers within the duration (in HH:MM: SS format) as specified by the user.
    • Rate: Releases the VUsers at the specified rate of VUsers per minute.
    • In specified multi-step duration: Releases the Vusers in the step mode.

 

  • Script(s) part of SyncPoint: It displays all the scripts that are part of Sync point. After specifying the required configuration, click Save to add the Sync point.

Sync Point Management

It has the following options:

Figure 179: Sync Point Management
  • Group Name: It shows the name of the group.
  • Type: Specify the type of sync point.
  • Name: Specify the name of the object (transaction/page/script/custom) on which SyncPoint is applied.
  • Active: Shows whether the sync point is enable or disabled.
  • Participating Vusers%: Percentage of Vusers participated for a specific Sync point. This percentage is calculated over the total number of Vusers in case of ALL groups.
  • Release Target Vusers: Specifies the number of Vusers that should reach a Sync point for releasing that Sync point.
  • Action: To add, release, update, delete, activate or deactivate the Sync point.
  • Mode: It is the way in which the Sync point is going to be released. This could be done either automatically or manually.
  • Release Type: It shows how the Vusers will be released
  • Schedule: It defines when the VUsers are released after they have reached their respective Sync point. 
  • Script: Specify all the scripts that are part of SyncPoint. Multiple script names can be provided as comma separated.
  • Once all the above fields are filled, click the Save Changes icon at the top right corner of the page.

Java Setting for Java Type Scripts

This section is used to perform the Java setting, if the user is using the java type script in the scenario. In this case, the user needs to set some arguments for the execution of java type script.

To access Java Settings, click the Additional Settings  in Scenario Reports as shown in Figure 116. On the additional settings page, select Java Settings as shown in below figure.

Figure 180: Java Settings

Java Settings Option

  • JVM Min and Max Heap Size: Java program executes in JVM and uses a heap of memory to manage the data. User can set minimum and maximum heap sizes accordingly.
  • JVM Virtual User Thread Pool: Specify the minimum and the maximum number of threads that are reserved for requests from applications. The thread pool is dynamically adjusted between these two values.
  • JVM Custom Arguments: This is used for passing multiple arguments and setting NJVM custom arguments.
  • System Java Class Path: The classpath is the path that the Java runtime environment searches for classes and other resource files. This is used to set the NJVM system classpath. The System class maintains a Properties object that describes the configuration of the current working environment.
  • Scenario Specific Class Path: This is also used to set the NJVM system class path. In this, a third party is also used.
  • Java Home Path: JAVA_HOME is an environment variable (in UNIX terminologies), or a PATH variable (in Windows terminology). This is used to set the NJVM Java Home path. Set the NJVM_JAVA_HOME environment variable to point to the JRE installation directory.
  • Connection Timeout: Connection time is the time for which NVM has to wait for NJVM to connect. The maximum time is 60 seconds. After 60 seconds, the connection breaks.
  • Message Timeout: Message timeout means when LOAD TEST sends a Request and the Server did not respond within the given time then error is displays as Timeout.

Once all the fields are filled click the  save changes icon at the top right corner.

 

Health Check Settings

To access Health Check Settings, click the Additional Settings  in Scenario Reports as shown in Figure 116. On the additional settings page, select Health Check Settings as shown in below figure.

Figure 181: Health Check Settings

The Health Check Settings window contains the following sections:

  • Controller Health
  • Generator Health
  • Other Settings

Controller Health

Disk

This section contains information on the disk space status, such as what is the total space of the disk for a particular file system, how much disk space is in use, and what is the free space currently.

Disk Options

  • File System: It contains a list of file systems available in NSAppliance/NDAppliance.
  • Current Disk Status: This field shows the total space, used space, and free space (in %) of the disk.
  • Threshold Free Space: The user can set the following threshold Free Space values (in %) for the disk:
  • Critical: It is used to specify the critical value (in %) below which the test should not run.
  • Major: It is used to specify that the free disk space percentage is nearing the critical value (in %) and that it has reached the major threshold.
  • Minor: It is used to specify that the free disk space percentage has just reached the minor threshold value (in %).
  • Start Test: Specifies whether the user wants to stop the test or not if the critical value is reached.
INode

In file system, an index node, informally referred to as an INode, is a data structure used to represent a file system object, which can be one of various things including a file or a directory. This section contains information on INode space, such as what is the total number of INodes allocated for a particular file system, how many INodes are in use, and what is the free INodes (in %) currently.

INode Options

  • File System: It contains a list of files system available in NSAppliance/NDAppliance.
  • Current INode Status (GB): This field displays total INodes, used INodes and free INodes (in %).
  • Threshold Free Space- User can set following threshold Free Space values (in %) for INode:
  • Critical: It is used to specify the critical value (in %) below which the test should not run.
  • Major: It is used to specify that the free INodes percentage is nearing the critical value (in %) and that it has reached the major threshold.
  • Minor: It is used to specify that the free INodes percentage has just reached the minor threshold value (in %).
  • Start Test: It is used to specify whether the user wants to stop the test or not if the critical value is reached.

Generator Health Options

  • Enable Generator Health Check before the start of the test. The test will not start, if any Generator Health Check fails.
  • Enter Min free disk size space in GB. By default, it is 10 GB.
  • Enter Max CPU utilization in terms of %.
  • Enter Min Available Memory in GB. By default, it is 4 GB.
  • Enter Min Interface speed in mbps.

Other Settings

Wait for connection to clear if reached a limit

In this section, a user can configure the number of connections allowed at a time while running a test. If it exceeds the specified limit, further connections are not established until the existing connections are released in the network.

Once all the above fields are filled, click the Save Changes  icon at the top right corner of the page.

NetDiagnostics Settings

Here the user needs to configure the NetDiagnostics setting for the scenario to configure the monitor and collect the data for monitoring. To access NetDiagnostics Settings, click the Additional Settings  in Scenario Reports as shown in Figure 116. On the additional settings page, select NetDiagnostics Settings as shown in below figure.

Figure 182: NetDiagnostics Settings

NetDiagnostics Settings Option

  • Topology Name: Select the existing topology of the monitors.
  • Enable NetDiagnostics data controller with profile: Select the profile which was created previously. Profiles are a set of configuration files that help ND Collector to identify the agent specific configuration.
  • Test Mode:
  • Inbound Mode: In inbound mode, The connection is made between CMON Agent and LoadTest.
  • Outbound Mode: In outbound mode, Net Diagnostic Controller(NDC) works as a server and CMON works as Client. CMON create connection with NDC. The first connection made b/w NDC and CMON is called “Control Connection”. After the first connection the CMON prepares itself to process and send the data to NDC. This connection is known as “Data Connection”. Now NDC will send the data to LoadTest.
  • Mixed Mode: This indicates the test will run in mix mode which may be the inbound or outbound method.

Session Restart Configuration on System Reboot

Select any of the following options:

  • Restart the Stopped and Running sessions: After the system reboot, it will restart stopped and running sessions.
  • Restart only the Running sessions: After the system reboot, it will restart all the running sessions.
  • Do not restart any session: After the system reboot it will not restart any session.

Once all the above fields are filled, click the Save Changes  icon at the top right corner of the page.

Network Simulation

Network simulation is a technique where a program models the behavior of a network either by calculating the interaction between the different network entities (hosts/packets, etc.) using mathematical formulas, or actually capturing and playing back observations from a production network. To access Network Simulation, click the Additional Settings  in Scenario Reports as shown in Figure 116. On the additional settings page, select Network Simulation as shown in below figure.

Figure 183: Network Simulation

Network Simulation Option

Provide details in the following fields for Network Simulation:

  • Enable Network Simulation:When enabled, user is simulated on different bandwidth and location.
  • Jitter:Jitter is defined as a variation in the delay of received packets. The sending side transmits packets in a continuous stream and spaces them eventually apart. Because of network congestion, improper queuing, or configuration errors, the delay between packets can vary instead of remaining constant. User have the following fields for jitter:
    • Network Jitter Forward:It is any deviation in, or displacement of, the signal pulses in a high-frequency digital signal from server to client.
    • Reverse:Specify the time difference of packets received at client side.
  • Adverse Factory Latency:Adverse factor for latency and packet loss: It is the variable percentage for latency and packet loss from server to client and vice versa.
  • Loss (%):Specify the packet loss in %.

Once all the above fields are filled, click the Save Changes  icon at the top right corner of the page.

User Profile

All users belonging to a scenario group share same common characteristics. These characteristics include:

  • Network Access method employed by the user to access the web application e.g., 56 K dial-up modem, 512K DSL, cable modem, T1 etc.
  • Geographic location of the users. For example, East Cost, mid-west, Asia etc. Geographic location affects the number of hops, packet loss etc.
  • Web Browser Used by users, such as NetScape4, IE 5.0 etc.

 

A common virtual user characterization of a scenario group is called User Profile. User Profile is used for WAN-ENV simulation and can be designed accordingly. User Profile can be designed with desired Location, Access, Browser and Co-located User for scenario groups.

A scenario group is associated with a single User profile. But multiple scenario groups may share same user profile. This happens in the situation when such scenario groups have different test script associated with them.

If the WAN Simulation is on, one important thing that needs to be defined for actual server is the physical location of the server (SUT) when deployed in production environment. By default, it is set to San Francisco.

By default, Internet simulation is disabled. So, all user profiles just boil down to a LAN. To use the real Internet simulation:

  • Enable the WAN simulation as described below.
  • Use the appropriate User profile in defining the Scenario groups.
  • Define the Location of the Server as described in the Server Configuration Section below.

There are following sections under this:

  • Profile
  • Location
  • Edit Access
  • Browser
  • Screen Size

A common virtual user characterization of a scenario group is called a User Profile. To access User Profile, click the Additional Settings  in Scenario Reports as shown in Figure 116. On the additional settings page, select User Profile as shown in below figure.

Figure 184: Profile(User Profile)

Profile

User Profile window is divided in to two frames:

  • User Profile Management Frame
  • User Profile Details Frame
User Profile Management Frame

A common virtual user characterization of a scenario group is called a User Profile. There are the following options:

With this frame, the user can perform following operations:

  • Select a user profile
  • Add a user profile
  • Copy a user profile
  • Delete a user profile

 

  • To Select User Profile- Select the pre-existing user profile from the drop-down available.

To Add a User Profile:

  1. Enter new user profile in the New User Profile
  2. Click the Addbutton.
  3. After clicking Add button, user gets the User Profile with its default values.
Figure 185: Add User Profile
  1. Specify the user profile details [discussed later].
  2. Click the Save button to save the user profile.

To Copy a User Profile:

  1. Select an existing user profile from the User Profile drop-down list.
Figure 186: Copy User Profile

2. Enter user profile name in New User Profile textbox to copy existed profile.

3. Click the Copy

4. Now, the selected user profile gets copied to name provided in New User Profile

To Delete a User Profile:

  1. Select the profile that needs to be deleted from the User Profile drop down list.
  2. Click the Delete
  3. Now, user profile gets deleted from the drop-down list.

User Profile Details Frame

With the help of this frame, users can add location, access, browser, and co-located users to a user profile. This frame is again divided into following four sub-frames.

  • User Location with Dedicated Access
  • Dedicated User Access
  • Location with Shared Access (Co-Located Users)
  • User Browser

Each of above sub frames is provided with three options Add, Delete, and Update.

  1. User Location with Dedicated Access
  • Location is the location name representing the geographical location of the users.
  • Percent is the percentage of this group of users with respect to total users.
  • To Add a Location in the User Location with a Dedicated Access frame
  • Select a location from drop-down list of user locations.
Figure 187: User Location with Dedicated access
  • Set Percent value of the selected location.
  • Click the Add button, location gets added in the list.
  • To Delete a Location from User Location with Dedicated Access frame
  • Select location row from user location list.
Figure 188: To Delete a Location from User Location
  • Click the Delete The location gets deleted.


User can delete multiple locations at a time by selecting multiple rows.

 

  • To Update a Location from User Location with Dedicated Access frame:

Select a row to be updated. Here, user can update percentage of users

Figure 189: Update User Location with Dedicated Access

Update the Percent value and click Update. The percent gets updated.

2. Dedicated User Access

In this frame, access is the shared network access representing the physical network access used by the users and percent is the percentage of this group of users with respect to total users.

The Dedicated User Access frame contains three buttons Add, Delete, and Update.

To Add an Access in Dedicated User Access frame:

  1. Select an access from drop-down list of user access.
Figure 190: Add Dedicated User Access

2. Set percent value to selected user access.

3. Click the Add The user access gets added in the list.


Total percent of added accesses should be 100.

To Delete an Access from Dedicated User Access frame:

  1. Select access row that needs to be deleted.
Figure 191: Delete Dedicated User Access
  1. Click the Delete The access gets deleted.


User can delete multiple Accesses at a time by selecting multiple rows.

To Update an Access from Dedicated User Access frame:

  1. Select a row from the drop-down list to be updated.
Figure 192: Update Dedicated User Access
  1. Change Percent value and click Update The access percent gets updated.
3. Location with Shared Access (Co-Located Users)

In this frame, access is the shared network access representing the physical network access used by the users. Location is location-name representing the geographical location of the users and percent is the percentage of this group of users with respect to total users. The Location with Shared Access frame contains three buttons Add, Delete, and Update.

To Add value in Location with Shared Access (Co-Located Users) frame:

  1. Select the location from drop-down list of locations, select the user access, and provide the percentage.
Figure 193: Add Location with Shared Access

2. Click the Add button, the record gets added.

 

To Delete a row from Location with Shared Access (Co-Located Users) frame:

  1. Select a row to be deleted.
Figure 194: Delete Location Shared Access

2. Click the Delete The selected row gets deleted.

To Update a row in Location with Shared Access (Co-Located Users) frame:

  1. Select a row to be updated.
Figure 195: Update Location Shared Access

2. Change Percent value and click Update The percent gets updated.

4. User Browser

User Browser drop-down contains a default list of Browsers. The User Browsers frame contains three buttons – Add, Delete and Update.

To Add a Browser in User Browser frame:

  1. Select a browser from drop-down list of user browser and specify the percentage.
Figure 196: Add User Browser

2. Click the Add button, the browser gets added in the list.



Total percent of added browsers should be 100.

To Delete a Browser from User Browser frame:

  1. Select browser row that needs to be deleted.
Figure 197: Delete User Browser

2. Click the Delete The browser gets deleted.



User can delete multiple Browsers at a time by selecting multiple rows.

To Update a Browser from User Browser frame:

 

  1. Select browser row that needs to be updated.
Figure 198: Update User Browser
  1. Update the Percent value and click the Update The percent value gets updated.

Click the Save Changes  icon on the top right corner of the page

Location

This section is used to add/delete/update a location. To setup Location (User Profile), click the Additional Settings   in Scenario Reports as shown in Figure 116. On the additional settings page, click on User Profile and select Location as shown in below figure.

Figure 199: Location

Add Location

  1. Enter the new location name and click Add.
  2. The following window is displayed:
Figure 200: Add Location

2. Add the location details, such as continent/country, city, longitude, and latitude.

Click OK. The location gets added to the list.

Mapping of Locations

User can map the location with forward and backward latency and forward and backward loss.

Steps to map a location:

  1. Select a location and click Add icon .
  2. Set values of ‘From Location’, ‘To Location’, ‘Forward Latency’, ‘Backward Latency’ and Loss for both the servers to be mapped and then click the OK.
Figure 201: Add Location Profile

Note: User can also Edit or delete location by clicking the or  icon respectively as per the requirement.

Access

Network Access method employed by the user to access the web application. This section is used to add/delete/update network access. This section is used to add/delete/update a location. To setup Access (User Profile), click the Additional Settings in Scenario Reports as shown in Figure 116. On the additional settings page, click on User Profile and select Access as shown in below figure.

Figure 202: Access( User Profile)

Adding an Access

  1. Enter the value in the following fields:
  • Access name: Enter the access name in the field.
  • Upload bandwidth: Select the upload bandwidth as per the requirement.
  • Download bandwidth: Select the download bandwidth as per requirement.
  • V.42 compression: Select whether you need the V.42 compression or not to access.
Figure 203: Add User Network Access

2. Click the Add button, the record gets added to the list.

Note: The user can update the upload bandwidth and download bandwidth settings.

User can also Edit or delete access by clicking the or  icon respectively as per the requirement.

Click the Save Changes  icon on the top right corner of the page.

Browser

Web Browser used by users, such as NetScape4, IE 5.0, etc. This section is used to add/delete/update a browser. To setup Browser (User Profile), click the Additional Settings  in Scenario Reports as shown in Figure 116. On the additional settings page, click on User Profile and select Browser as shown in below figure.

Figure 204: Browser( User Profile)
Adding a User Browser Type
  1. Fill in the following fields:
  • Browser Name: Enter the browser name in this field.
  • Max Con Per Server(HTTP1.0): Maximum connection per server for HTTP 1.0.
  • Max Con Per Server(HTTP1.1): Maximum connection per server for HTTP 1.1.
  • Max Con Per Proxy(HTTP1.0): Maximum connection per proxy for HTTP 1.0.
  • Max Con Per Proxy(HTTP1.1): Maximum connection per proxy for HTTP 1.1.
  • Max Con Per User: Enter the maximum connection per user.
  • Keep Alive Time: It shows the connection alive time.
  • User Agent String: The User-Agent string is intended to identify devices requesting online content.
Figure 205: Add Browser Type
  1. Click OK button, the user browser gets added.

Click the Save Changes icon on the top right corner of the page.

Screen Size

This provides the screen size, such as 1920*1080 where 1920 is (width * height) and 1080 is the pixels. This section is used for editing a screen size. To setup Screen Size (User Profile), click the Additional Settings  in Scenario Reports as shown in Figure 116. On the additional settings page, click on User Profile and select Screen Size as shown in below figure.

Figure 206: Screen Size

Screen Size Options

This window contains the following options:

System Default Screen Size Settings: This shows System Screen Size setting which includes different Screen Size in pixels and corresponding Percentages of it. Total percentage is 100.

User Profile Default Screen Size Settings: This is the default settings for user profile screen size. In this, select the user profile from the Select User Profile drop-down list to which this screen size to be applied and then select the Screen Size and provide the percentage. After Add operation, it is added and it shows the percentage whatever user wanted to add.

Figure 207: User Profile Default Screen Size

User can also Edit or delete Screen Size by clicking the or  icon respectively as per the requirement.

Click the Save Changes  icon on the top left corner of the page once all the fields are filled.

Global Data Directory

To access Global Data Directory, click the Additional Settings  in Scenario Reports as shown in Figure 116. On the additional settings page, select Global Data Directory as shown in below figure.

Figure 208: Global Data Directory
Global Data Directory Option
  • Select Global Data Directory: Users can select any data directory that will use in the script by default.
  • Override all data directories (including custom) in all scenario groups: If you override the data directory, the data files of all file parameters are taken from the specified directory. If no file is found, it will be taken from the data directory specified in the file parameter and then from the script directory. By enabling the options user can override the data directory in every group with the default data directory.

Advanced

To access Advanced Settings, click the Additional Settings  in Scenario Reports as shown in Figure 116. On the additional settings page, select Advanced Settings as shown in below figure.

Figure 209: Advanced Settings

Advanced Options

  • No of Virtual Machine(s): Virtual machines are child processes that are created by LOAD TEST parent process to distribute the load (users/sessions) among them. There are two fields first one for count and second one to select either Machine or CPU.
  • Selecting the CPU option, displays the Min Session Rate/Users per Virtual Machine field where you can specify the minimum number of users in a session.
  • Machine: Number of Virtual Machines = Given count.
  • Copy Script in test run: When enabled, all the scripts are copied in the Testrun. When “Exclude Dump” option is enabled, dump files are skipped while copying the script in test run.
  • Auto scale Cleanup: With this setting, a user can perform auto scale cleanup from UI. A new GDF is created on partition switch and a message is sent to get inactive nodes to NDC in the specified time interval.

Optimize Ethernet packet flow

  • User can optimize the Ethernet packet flow by using the following options (By default, 10 packets are exchanged between client and server):
Figure 210: Optimize Ethernet Packet Flow
  • Handshake Merge Ack: It reduces 1 packet, 9 packets are exchanged between client and server (packets 3 and 4 are merged into a single packet).
  • Data Merge Ack: It reduces 1 packet, 9 packets are exchanged between client and server (packets 7 and 8 are merged into a single packet).
  • Close by Reset: It reduces 2 packets, 8 packets are exchanged between client and server (packets 8, 9, and 10 are merged into a single packet).

User/Session distribution (%) over NVMs

 It contains following options:

  • Distribution for maximum performance. A scenario group may be distributed over 1 or more NVMs: All Users/Sessions is distributed over 1 or more NVMs as per the setting in Number of virtual Machine.
  • Distribution for maximum isolation among scripts. All scenario groups using the same script is executed only by one NVM: Users/Sessions of the same script is assigned to one NVM (Number of Virtual machines= different number of scripts used in scenario file).
  • User specifies NVM Id for each scenario group: Users/Sessions of same cluster id is assigned to one NVM (Number of Virtual Machines = different number of cluster IDs).
Figure 211: User/Session Distribution(%)

Virtual User Thread Pool

It is a collection of Virtual users where each VUser is considered a thread. It is used for ramping up/ramping down users as specified in the scenario when the script is run in thread mode.

     The user needs to provide the following inputs:

  • Initial number of threads: Initial number of threads to be used in the test.
  • Increment By: How many threads are to be increased when the initial gets exhausted.
  • Max: Maximum number of threads to be used for a test.
  • Thread stack size: Stack of each thread in KBs.
Figure 212: Virtual User Thread Pool
  • Maximum number of dynamic hosts: Maximum number of different hosts allowed to connect.
  • Maximum Number of Concurrent Sessions: It defines the number of concurrent sessions that need to be executed. Only a defined number of sessions runs parallel, the rest are in a Blocked state.

Test on Generator failures

  • Stop test on Controller if one (or more) of the following thresholds are breached. It will stop the test on the controller as per the threshold.
  • Stop test on Generator if one (or more) of the following thresholds are breached. It will stop the test on the Generator as per the threshold.
Figure 213: Test On Generator Failures 

TCP Connection Port Selection Settings

Socket Binding is the process of allocating a Port number to a Socket to address a network within a system.

Figure 214: TCP Connection Port Selection

There are following options:

  • Mode for Port Selection: Selection of the Port is either ‘Sequential’ or ‘Random’ mode. By default, it is Sequential Mode.
  • Number of retries on socket Bind Failure: Number of retries to be attempted once bind failed on the socket. After retry attempt exhaustion, the provided action is implemented.
  • Action to be taken on failure: When retry attempts are exhausted, action is taken according to the option applied. Options can be ‘Enable’ or ‘Disable’.

Capture TCP dump for controller/generators Communication Troubleshooting

  • It is the condition of capturing the TCP dump. It will capture the TCP dump on Generator/Controller accordingly.
Figure 215: Capture TCP Dump for Controller

IO Vector

It is the configuration setting of the IO vector used by LOAD TEST for sending requests on socket.

Figure 216: IO Vector Settings

There are following fields:

  • Initial Vector Size: Initial number of allocated IO vectors. Cannot be less than 100.
  • Increment By: Increment size for reallocating IO vectors. Should be greater than 0 and less than max.
  • Maximum Size: Maximum number of IO vectors that can be allocated for the whole test.

Whitelist Http Header

Figure 217: Whitelist HTTP Header
  • Name: Enter the user agent name.
  • Value: Enter the whitelist http header value.

 

Override Dashboard Default Favorite

  • By selecting this option, you can change the default favorite option. The selected favorite will be applied in all the test runs generated using this scenario. This option will override the default favorite configured in the Organized Favorite Window.
Figure 218: Override Dashboard Default Favorite

Ports for Generator to Controller Communication

In some cases, where firewall is present between generators and controller which can give an error in making connection from generator to controller. So, we need to enable the firewall for the port range. The default range is set to 7914 to 7920.

When none of the ports from the above range is available then user can also select the checkbox to use system assigned port. If they don’t select this checkbox, then test will stop.

Note At least 3 ports are needed in the port range.

Figure 219: Ports for Generator to communication
Previous
Next