Testing CPU Loads for Replication

Perform a mixed-load test to ascertain whether the throughput to the cache and EIS is sufficient. Do this by testing then observing CPU load trends.

1. Run a typical application maximum mixed-load test on the Unwired Server (5% initial sync, 95% subsequent sync) and observe the cache CPU load.
   Do not run this mixed-load test against Relay Server; you want to first ascertain the maximum throughput of just the Unwired Server and cache.
2. If the cache CPU load is too high, too many threads could be impacting performance:
   1. Decrease the replication thread count on each server in Sybase Control Center.
   2. Restart all servers.
   3. Observe the cache CPU load again.
3. If the cache CPU load is low, fine tune the replication thread count until one yields the maximum through put. Check this by:
   1. Note the client response times of other synchronization types and try increasing the replication thread count in small increments.
      Other types of synchronization include initial to initial, subsequent to subsequent, similar payload, cache policy, and so on.
   2. Repeat this process until the synchronization response times are as low as possible for the same number of clients for all types of synchronizations.
      Once the relative client response time is as low as possible without further increasing the replication thread count, you have reached the configuration that yields the maximum throughput. In other words, tune the thread count to yield the best overall response times. Usually, this thread count number is small.
4. Repeat the mixed-load test on EIS backends.
   This checks for EIS latencies and cache policies, both of which can change the performance of the server cluster.
5. Introduce relay server into the environment, and repeat the mixed-load test.
6. Once the environment has stabilized and tuned, enable on and configure only the monitoring profiles you need.