Tuning Synchronization for Messaging Payloads

If your application synchronize over the messaging payload protocol, tune your production environment after all components have been deployed and started.

  1. Isolate the monitoring database from the cache server.
    See Isolating and Setting Up Production Monitoring Databases.
  2. Disable all enabled monitoring profiles that currently exist.
    Normally, monitoring in a cluster configuration occurs at two levels — the cluster and the domain. Sybase recommends that you turn off monitoring when assessing performance.
    1. In navigation pane of Sybase Control Center, click Monitoring.
    2. In the administration pane, select the profile name and click Disable.
    3. Validate that all monitoring is disabled by opening <UnwiredPlatform_InstallDir>\Servers\UnwiredServer\Repository\Instance\com\sybase\sup\server\monitoring\ MonitoringConfiguration\domainLogging.properties, and verifying that “status”, “enabled”, and “autoStart” are set to false.
    See Monitoring Profiles in the Sybase Control Center online help.
  3. Stop all Unwired Servers in your cluster(s).
  4. In Sybase Control Center, change the number of outbound and inbound queues to 100 each for each Unwired Server.
    1. In the left navigation pane, click Servers > SeverName > Server Configuration.
    2. In the right administration pane, click General > Performance.
    3. Change the default values for inbound and outbound queues to 100 each.
    4. Optionally, configure these other properties:
      • Maximum Number of In Memory Messages – specify the number of in-memory messages to allow.
      • Subscribe Bulk Load Thread Pool Size – the maximum number of threads allocated to initial bulk load subscription operations. The default value is five. Setting the thread pool size too high can impact performance.
    5. Repeat for all servers in all clusters.
  5. Restart all servers in your cluster(s).
  6. In Sybase Control Center, deploy and test a messaging package with a representative amount of data for initial subscription.
    For details, see Deploying and Managing MBO Packages.
    For example, if the use case dictates that during an initial subscription, the mobile application is to receive 2MB of data, develop the test package to reflect that fact.
  7. Start testing by using expected number of devices to perform an initial subscription, and determine if the time to get the initial data set is satisfactory for all devices.
    The maximum messaging throughput is 70 messages per second in a wired environment.
    • If the calculated throughput for the test is below this number, it is likely that the connection method (as opposed to the server environment) is the limiting factor. In this case, more devices can be supported without any degradation in server performance.
    • If the test reaches the maximum throughput, the number of devices performing the initial subscription is the maximum one server can handle. Add another server to the cluster for additional message processing power (up to a 60% increase).