Performance Tuning Siebel Software on the Sun Platform

More documents

Recommendations

Info

Sun Storage: Oracle database files were laid out on a Sun StorEdge SE6320 system. I/O balancing was implemented on the <strong>Siebel</strong> workload to reduce hot spots. Also zone bit recording was used on disks to provide higher throughput to the <strong>Siebel</strong> transactions. Direct I/O was enabled on certain Oracle files and on the <strong>Siebel</strong> file system. More details on this topic are available in Section 7.6.2. Connection Pooling: <strong>Siebel</strong>’s database connection pooling was used, providing good benefits for CPU and memory. Twenty end users shared a single connection to the database. More details on this topic are available in Section 7.7. Usage of Appropriate Sun Hardware: Pilot tests were performed to characterize the performance of the web, application, and database across the current Sun product line. Hardware was chosen based on best price/performance rather than pure performance. Details on this topic are available in Section 3. <strong>Performance</strong> <strong>Tuning</strong> <strong>Siebel</strong> <strong>Software</strong> on the Sun Platform Page 8
2 <strong>Siebel</strong> Application Architecture Overview <strong>Siebel</strong> server is a flexible and scalable application server platform that supports a variety of services operating on the middle tier of the <strong>Siebel</strong> N-tier architecture, including data integration, workflow, data replication, and synchronization service for mobile clients. Figure 2.1 provides a high-level view of the <strong>Siebel</strong> application suite architecture. Figure 2.1 <strong>Siebel</strong> server includes business logic and infrastructure for running the different CRM modules as well as connectivity interfaces to the back end database. It consists of several multithreaded processes commonly referred to as ‘<strong>Siebel</strong> Object Managers’. These can be configured so that several instances of it can run on a single Solaris machine. The <strong>Siebel</strong> 7.x server makes use of gateway components to track user sessions. <strong>Siebel</strong> 7.x has a thin client architecture for connected clients. The <strong>Siebel</strong> 7.x thin client architecture is enabled through the <strong>Siebel</strong> plug-in (SWSE – <strong>Siebel</strong> Webserver Extension) running on the web server. It's the primary interface between the client and the <strong>Siebel</strong> <strong>Performance</strong> <strong>Tuning</strong> <strong>Siebel</strong> <strong>Software</strong> on the Sun Platform Page 9
Page 1 and 2: Performance <stron
Page 3 and 4: Abstract This paper discusses the p
Page 5 and 6: 7.6.6 Oracle Parameters Tun
Page 7: 1 Tuning for Price
Page 11 and 12: 3 Optimal Sun/Siebel</stron
Page 13 and 14: 3.1 Hardware and Software</
Page 15 and 16: 5 10,000 Concurrent Users: Test Res
Page 17 and 18: 6 Siebel Scalabili
Page 19 and 20: Cost per Siebel Us
Page 21 and 22: 7.1 Tuning Solaris
Page 23 and 24: 7.1.3 The Solaris Kernel and TCP/IP
Page 25 and 26: In the file $SIEBEL_ROOT/bin/enu/ua
Page 27 and 28: 7.2.3 Assignment Manager Tu
Page 29 and 30: MQ series parameter tuning: PERFQMG
Page 31 and 32: Investigating the Reason for the Fa
Page 33 and 34: let a Siebel proce
Page 35 and 36: Description The reason for this sym
Page 37 and 38: Parameter Scope Default Tuned Value
Page 39 and 40: 7.6 Tuning <strong
Page 41 and 42: 86 MB/second 57 MB/second Figure 7.
Page 43 and 44: DATA_51200K INDX_512K DATA_5120K TE
Page 45 and 46: 7.6.4 Solaris MPSS Tuning</
Page 47 and 48: Siebel Object Name
Page 49 and 50: instance_name=oramst job_queue_proc
Page 51 and 52: ORAPERF.S_PRI_LST T4 WHERE T4.PAYME
Page 53 and 54: the database during peak load. In t
Page 55 and 56: use connection pooling, so you woul
Page 57 and 58: Oracle Database Server 1. Larger th
Page 59 and 60:
160 siebelapp2_1 eSalesObjMgr_enu 1
Page 61 and 62:
9.10 To Produce a Stack Trace for t
Page 63 and 64:
Count indv cuml rcnt nsec Lock Call
Page 65 and 66:
5. Once the user has stopped at the
Page 67 and 68:
10 Appendix A: Transaction Response
Page 69 and 70:
eSls1_115DDSubCategory1.3 0.125 0.1
Page 71 and 72:
CC3_2newSolution 0.047 0.136 3.281
Page 73 and 74:
11 Appendix B: Database Objects Gro
Page 75 and 76:
S_OPTY_BU_M8 INDEX 2,334,720 S_ORDE
Page 77 and 78:
log file parallel write 550,101 515
Page 79:
Acknowledgements Thanks to
show all

Performance Tuning Siebel Software on the Sun Platform

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?