If the package history does not reveal a high amount of volume (data or frequency of operations), proceed with evaluating the package statistics for the entire environment. Package statistics can reveal issues caused by the number of device users in the environment, and how the package is performing in environment in general.
- In Sybase Control Center, click the Monitoring node, then click the Package Statistics tab.
- Choose the type of package you want to retrieve KPIs for: messaging or replication.
- Set the Start Date, Start Time and Finish Date, Finish Time so KPIs are aggregated during the specified time frame.
- In the navigation tree, expand clusters, domains, and servers, until you locate the package to investigate.
- Click the package name and review:
- Total Data Push
- Time at Minimum/Maximum/Average Synchronization
- Total Devices
Compare the findings to see whether or not these results are revealing. Also check the number of concurrent users so you can gauge the full range of activity (for example, use the navigation tree to scope data push results to the domain and cluster): if multiple device users are using similar packages to synchronize a similar set of data, then your system could be experiencing lags due to high demands on the server cache.
Next
If package statistics do not provide useful information about data demands, evaluate the data demands of individual users.