If the application is not downloading large amounts of data, further investigate user-based key performance indicators (KPIs) to see if the performance issue is related to the user who is performing some other data-related action that may not be related to the package for which the issue was reported.
- In Sybase Control Center, click the Monitoring node, then click the User Statistics tab.
- Choose the type of package for which to retrieve KPIs: messaging or replication.
- Set the Start Date, Start Time and Finish Date, Finish Time so KPIs are aggregated for the specified time frame.
- If the package is deployed to a particular domain, choose the domain name you require.
- Select the user who reported the issue.
- Review these values :
- Total Data Push
- Time at Minimum/Maximum/Average Synchronization Time
A high data push value might indicate that at some point, data demands were large. If the average synchronization and minimum synchronization times fall within normal ranges but the maximum is high, it may indicate that data volumes have created a synchronization performance lag for the package. Low data delivery for the package (determined during package-level analysis), but high values for the individual user may suggest an unusual demand pattern which may be harmless or require further investigation. Simultaneous synchronization demands may be impacting the performance of all applications on the device.
Next
If user data demands reveal no abnormalities, continue by checking administration data in other areas of Sybase Control Center, such as Device User administrative data and subscription configuration.