Tuning Synchronization for Replication 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 and domain logging databases from the cache server.
    This isolation only needed if you are using monitoring and domain logging in the production system, and want to reduce any database or storage contention. 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. 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. In Sybase Control Center, stop all Unwired Servers in all clusters.
  4. Stop the cache service on the data tier node.
  5. Use the dblog utility to isolate the cache disk and log on to fast storage.
    For details, see Using a Different Database and Log Path.
  6. Set new cache thread count, pool size, and initial cache size values.
    See Changing the Cache Database Server Thread Count and Managing Connection Pools for Unwired Server Connections .
  7. Restart the cache service and all Unwired Servers.
  8. In Sybase Control Center, update the Unwired Server replication synchronization properties on the primary server.
    1. In the left navigation pane, click Servers>SeverName>Server Configuration.
    2. In the right administration pane, click the Replication tab.
  9. In Sybase Control Center, set thread stack size and JVM heap sizes for the server.
    1. In the left navigation pane, click Servers>SeverName>Server Configuration.
    2. In the right administration pane, click the General tab then click Performance Configuration.
    3. Adjust the thread stack size and JVM heap sizes to the new values.
      • Thread Stack Size – the JVM -Xss option.
      • Minimum Heap Size – the minimum size of the JVM memory allocation pool, in megabytes. For production recommendations on this value, see Unwired Server Replication Tuning Reference in System Administration.
      • Maximum Heap Size – the maximum size of the JVM memory allocation pool, in megabytes. For production recommendations on this value, see Unwired Server Replication Tuning Reference in System Administration.
      • User Options (in Show optional properties) – other JVM options. For example, you can enable JVM garbage collection logging by setting -XX:+PrintGCDetails. Or you can set the permanent space which allocated outside of the Java heap with DJC_JVM_MAXPERM; the maximum perm size must be followed by K, M, or G, for example, -XX:MaxPermSize=512M. Note that DJC_JVM_MAXPERM is not visible to Sybase Control Center.
    4. Repeat for all servers.
  10. Restart all Unwired Servers.
Parent topic: Unwired Server Replication Tuning Reference