Tuning Synchronization for Messaging Payloads

If your applications 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 the Monitoring and Domain Logging Databases from Cache and Messaging 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. SAP recommends that you turn off monitoring when assessing performance.
    1. In navigation pane of SAP 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 SMP_HOME\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 SAP Control Center for SAP Mobile Platform.
  3. Stop all SAP Mobile Servers in your cluster(s).
  4. In SAP Control Center, change the number of outbound and inbound queues to 100 each on the cluster.
    1. In the left navigation pane, click Configuration.
    2. In the right administration pane, click the General tab.
    3. Select Performance from the menu bar.
    4. Change the default values for inbound and outbound queues to 100 each.
  5. Restart all servers in your cluster(s).
  6. In SAP Control Center, deploy and test a messaging package with a representative amount of data for initial subscription.
    For details, see Deploying MBO Packages and MBO Package Management in SAP Control Center for SAP Mobile Platform.
    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).
Parent topic: Performance Considerations for Messaging
Related tasks
Configuring Java Virtual Machine Performance Properties