Bookshelf Home | Contents | Index | Search | PDF

Siebel ePharma Handheld Guide for Windows-Powered Devices > Troubleshooting > Performance >

Server Performance

---

Server performance affects the performance and scalability of Direct Server Sync processes. Customers should engage Expert Services to do a Scalability Review. The following guidelines are general in nature and pertain to the Siebel Handheld sync components running on a Siebel Server:

Use Performance Monitor to track memory and processor performance on the Siebel server.
Make sure that the Servers (IIS, GW, OM and DB) are on the same high speed LAN segment.
Siebel Handheld Sync components will stress Siebel Server and database performance because of the intensive interactions during large concurrent synchronizations.
Estimate that 64 MB is used per Siebmtsh.exe instance.
To calculate the theoretical maximum concurrent users:
Numusers=Server_Memory*threads_per_process_ratio/64 MB.
Optimize the Threads per Process Ratio (Max Tasks/Max MT Servers) per Technical Note 405, Siebel Handheld Synchronization.
Set Max Tasks=Max. number of concurrent users (for example, 150).
Set MinMTServers=MaxMTServers (for example, 30 for 5:1 ratio, if this is determined to be appropriate).

To optimize and tune a Siebel DB server:

Use Performance Monitor to track memory and processor performance on the DB server.
Turn on SQL tracing and search for long-running SQL calls.
Estimate 64 MB of RAM for each concurrent user.
Consider creating indexes to tune the queries (only performed with the assistance of Siebel Expert Services).
Consider using a RAID 0+1 disk array with an expanded number of spindles to optimize database performance.

NOTE:  Make sure that DB Server settings are set to recommended values. Timeouts should be set at the Siebel Server. Be careful that the timeout is set longer than the longest SQL query.

Bookshelf Home | Contents | Index | Search | PDF