Available in: Axsy Mobile for Salesforce, Axsy Field Service, Axsy Public Sector, and Axsy Retail Execution
All Axsy mobile apps are designed for offline-first use and as such they must synchronise the data they need from the Salesforce platform onto the mobile device before being used. When a user first logs onto their Axsy mobile app, an initial sync takes place that prepares the mobile app for subsequent offline use. The initial sync is the largest synchronisation event that the mobile app must perform (all other synchronisation events are incremental) while the user remains logged into the mobile app.
The Axsy Config Tool allows Salesforce administrators to define the amount of data that is synchronised to users 'mobile devices. Administrators should refer to the benchmark data in this article once they have defined their sync config scope to predict the impact of the initial sync in relation to:
Initial sync duration
Mobile device battery consumption.
Axsy used a range of devices for benchmark testing from the recommended devices list. The mobile operating system versions used were either the most recent major version or the immediately prior major version.
For the purposes of benchmark testing, the network conditions used in Axsy testing were typical of real world 4G mobile networks with 20 Mbps download and 5 Mbps upload speeds. Any improvement on 4G network speeds provides a negligible improvement in sync performance.
Assuming 4G or better network speeds, The most significant factor affecting the initial sync duration is the processing power of the mobile device. The industry standard Jet Stream 2 index was used to determine the processing power of the test mobile devices.
Battery consumption is mostly proportional to the duration of the initial sync – longer sync durations correspond to greater battery usage, but battery consumption is also affected by the capacity of the battery, battery health (age) and screen brightness to lesser degrees.
Battery consumption figures are therefore provided as an expected range instead of exact figures due to the number of factors affecting battery usage.
A range of test scenarios shown below in Table 2 were used for benchmarking purposes.
Table 2 – Test Record Scenarios
Benchmark 1: Initial Sync Duration
Benchmark results are shown for iOS, Android and Windows Retail Execution mobile apps. The sync durations are average values and may vary by up to 10%.
Reference App: Axsy Retail Execution v5.9.8.
Table 3a – iOS Initial Sync Durations
Figure 1a – iOS Initial Sync Durations
Reference App: Axsy Retail Execution v5.9.8.
Table 3b – Android Initial Sync Durations
Figure 1b – Android Initial Sync Durations
Reference App: Axsy Retail Execution v5.9.6.
Table 3c – Windows Initial Sync Durations
Figure 1c – Windows Initial Sync Durations
Benchmark 2: Battery Consumption
Table 4 – Battery Consumption
- How do I apply the benchmark results to my sync scope and mobile devices?
To determine the initial sync duration of your mobile devices, select the test record scenario closest to your sync scope and determine the Jet Stream 2 index for your mobile device. Then use Tables 3a—c and / or Figures 1a—c and Table 4 to determine your expected initial sync duration and battery consumption respectively. If necessary you may need to interpolate between values or extrapolate beyond the scope of the data presented in Tables 3a—c / Figures 1a—c and Table 4.
- How do I Determine the Initial Sync Duration?
Initial sync durations are determined from the Admin Console, see Figure 2 below for details.
Figure 2 – Initial Sync Duration Obtained from the Admin Console
- How do I Measure Battery Consumption?
Battery consumption is determined by before and after the initial sync by inspection of the mobile device battery bar, see Figure 3 for example screenshots taken once the initial sync commences and after it has completed.
Figure 3 – Viewing Battery Usage Before and After Initial Sync
- How do I find the exact number of records synced in the initial sync?
You can determine the exact number of initial sync records from the mobile app, navigate to the Synchronise page via the gear icon and then pick the History tab – the number of records will be listed there. See Figure 4 below for an example.
Figure 4 – Initial Sync Number of Records From the Mobile App
- What if my sync results do not match the figures provided?
Check your test conditions carefully, including:
- Ensuring an accurate Jetstream 2 index by not using the mobile device for other purposes while the test is running
- Checking your network speed is at least 20 Mbps download / 4 Mbps upload
- Checking the number of records you are actually syncing (see FAQ 4)
- Not using your mobile device for any other purpose while the initial sync is in progress
- Not letting the mobile device go into background mode while the initial sync is in progress.