User workloads are defined as follows:
Table 3. User Workload Definitions
||Includes NetScaler Gateway logons, enumerations, device registration, and so on for each session.
|Worx Store launches
||Users launch Worx Store multiple times and each time they subscribe to or install more than one app regardless of whether it is a mobile app (web/SaaS/MDX) or a Windows app (HDX).
|Web/SaaS app SSO per device
||Accounts for the launch sequence of web/SaaS apps up to the point where XenMobile completes the SSO and returns the actual app URL. Traffic was not sent to actual apps.
|MDX app downloads per device
||Counts of the number of MDX app downloads (this can happen across Worx Store launches). For iOS, this also includes the automation of app installation from Apple ITMS, which leverages the new token/tms service APIs on NetScaler Gateway.
Notes and Assumptions
In order to scale XenMobile beyond 30,000 devices, you should tune the following server parameters:
Config File - /opt/sas/sw/tomcat/inst1/webapps/ROOT/WEB-INF/classes/push_services.xml
- <property name="heartbeatFrequency" value="24" />
Config File - /opt/sas/sw/tomcat/inst1/webapps/ROOT/WEB-INF/classes/ew-config.properties
You should make these changes on all XenMobile nodes and then restart the server.
The following scenarios are not covered as part of the scalability tests. These scenarios would be considered for future enhancements in scale tests :
- Policy Push to device is not tested.
- Android Connected Devices not tested.
- Package deployment is not tested.
- Windows platform is not tested.
Each XenMobile supports a maximum of 10,000 connections simultaneously.
Tests were run in ideal conditions on LAN to ignore network latency issues. In a real world scenario, the scalability also depends on the user bandwidth available, especially for app downloads.
On-Boarding (FTU) Workload
The On-boarding (FTU) workload is defined as the first time a user accesses the XenMobile environment. Operations included in this workload were:
- Auto discovery
- Device registration
- Application delivery (web, SaaS, and mobile MDX apps)
- App subscription (including images and icon downloads)
- Installation of the subscribed MDX apps
- App launch (web, SaaS, and mobile MDX apps)
- Minimal WorxMail and WorxWeb connections (VPN tunnels) — two connections
- Installation of required apps through XenMobile
The workload parameters included:
- 1 device registration per device
- 1 enumeration per device
- 14 apps enumerated per device
- 4 Worx Store launches per device
- 4 web/SaaS app SSOs per device
- 1 MDX app downloaded per device
- 2 required app downloads
Existing Users Workload
The following table shows the Existing Users workload. This workload simulated a user using WorxMail and WorxWeb apps. This simulation was used to measure the NetScaler Gateway port's scalability within the XenMobile configuration. For the WorxWeb app, users were accessing internal web sites, which do not trigger XenMobile SSO. Operations in this mode included:
- Authentication (NetScaler Gateway and XenMobile)
- WorxMail and WorxWeb connections (VPN tunnels) — four connections
WorxApps Connection Profiles
The following table shows the workload parameters for existing users.
Table 4. WorxApps Connection Profiles
||Data sent per session1
||Data received per session1
|WorxMail Connection #1
|WorxMail Connection #2
|WorxWeb Connection #1
|WorxWeb Connection #2
|Total bytes transferred per session1
||~ 40.7 MB
1. Per session: 8 hours.
2. Type 1: Asymmetric send and receive with long lived connections (that is, WorxMail with a dedicated Microsoft Exchange mailbox connection).
3. Type 2: Asymmetric send and receive with connections that close and reopen after delays (that is, WorxWeb connections).
Note: Modifications to the connection details affect analysis results. For example, if the number of connections per user is increased, then the number of NetScaler Gateway sessions supported may be reduced.
WorxMail and WorxWeb Profiles
The following tables show the WorxMail and WorxWeb profile details.
Table 5. WorxMail Profile for a Medium Workload
|Messages sent per day
|Messages received per day
|Messages read per day
|Messages deleted per day
|Average message size (KB)
Table 6. WorxWeb Profile for Medium Workload
|Number of web apps launched
|Number of web pages opened manually
|Average number of request–response pairs per web app
|Average size of request (bytes)
|Average size of response (bytes)
Configuration and Parameters
The following configurations were used when running the scalability tests:
- NetScaler Gateway and load balancing (LB) virtual servers coexisted on the same NetScaler Gateway appliance.
- A 2048-bit key was used on NetScaler Gateway for SSL transactions.