Performance Tuning Siebel Software on the Sun Platform

More documents

Recommendations

Info

The procedure to list/change the parameter requests for <strong>Siebel</strong> server follows: 1. Connect to server manager at applications server level. 2. srvrmgr:siebapp2> list param Requests for comp WorkMon PA_ALIAS PA_VALUE PA_DATATYPE PA_SCOPE .. PA_NAME -------- -------- ----------- --------- ---------------------- Requests 5000 Integer Component .. Requests per iteration 1 row returned. 3. srvrmgr:siebapp2> change param Requests=20 for comp WorkMon Command completed successfully Note: To see the entire list of parameters for comp WorkMon, type the following: srvrmgr:siebapp2> list param for comp WorkMon 7.2.4 EAI-MQseries The <strong>Siebel</strong> 7.5 EAI MQ Series Adapter read from and placed transactions into IBM MQ Series queues. This test is designed to receive 400,000 messages from IBM MQ series into the <strong>Siebel</strong> application. Messages are divided into different categories depending on the type of operations they perform during receive. This test stresses the file system on which the queues reside by performing about 10% database inserts and 10% updates. Persistent queues are used. As a result, the database tuning and disk layout explained in this document are key for performance. To achieve best throughput the following setup was done: Minmtservers=maxmtservers=1, Maxtasks=45 for component MqSeriesSrvRcvr on the <strong>Siebel</strong> server. Moving the following directories to a different disk helped to improve performance by alleviating I/O bottlenecks: /mqm/qmgrs/PERFQMGR/queues/SENDQUEUE - Sendqueue /mqm/qmgrs/PERFQMGR/queues/RECEIVEQUEUE - Receivequeue /mqm/qmgrs/PERFQMGR/queues/LOG(ACTIVE) - Active Logs <strong>Performance</strong> <strong>Tuning</strong> <strong>Siebel</strong> <strong>Software</strong> on the Sun Platform Page 28
MQ series parameter tuning: PERFQMGR.OAMPipe_msg=2000000 (changed from default) in file /var/mqm/qmgrs/PERFQMGR/qmstatus.ini LogBufferPages=512 (changed from default 17) in file /var/mqm/qmgrs/PERFQMGR/qm_ini logPrimary files=12 (default value 2) LogSecondaryfiles=2 (default value 2) Logfilepages =1024 (changed to 16384(max)) Logtype=CIRCULAR(default CIRCULAR) From all of the above tweaks, a performance improvement of 35% in throughput was measured. Note: It was discovered during the benchmark that MQ Series version 5.1/5.2 has a 640,000 message limit, while 5.3 does not. 7.2.5 EAI-HTTP Adapter The <strong>Siebel</strong> 7 EAI-HTTP Adapter executed requests between different web infrastructures. <strong>Siebel</strong> EAI-HTTP Adapter Transport Business Service lets one send XML messages over HTTP to a target URL (web site). The <strong>Siebel</strong> Web Engine serves as the transport to receive XML messages sent over the HTTP protocol to <strong>Siebel</strong>. The <strong>Siebel</strong> EAI compgrp is enabled on one appserver and the HTTP driver is run on a Sun Fire v65/Windows XP machine. To achieve the result of 287,352 business transactions/hour, 4 threads were run concurrently, where each thread worked on 70,000 records. The optimum values for the number of <strong>Siebel</strong> servers of type EAIObjMgr for this workload were: MaxMTServers=2 minmtservers=2 MaxTasks=10 The other <strong>Siebel</strong> OM parameters for EAIObjMgr are best left at default; changing SISPERSISSCON to anything from default of 20 does not help. All of the Oracle database optimizations explained under that section in this paper helped achieve the throughput of 79 objects/sec. The HTTP driver machine was maxed out, causing slow performance. The reason for this was I/O, as the HTTP test program was generating about 3Gbytes of logs during the test; once this was turned, off as shown below, performance improved. driver.logresponse=false driver.printheaders=false The AnonSessionTimeout and SessionTimeout values in the SWSE were set to 300. HTTP adapter (EAIObjMgr_enu) tunable parameters: ● MaxTasks - Recommended value at the moment: 10 ● MaxMTServers, MinMTServers - Recommended value: 2 <strong>Performance</strong> <strong>Tuning</strong> <strong>Siebel</strong> <strong>Software</strong> on the Sun Platform Page 29
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 and 8: 1 Tuning for Price
Page 9 and 10: 2 Siebel Applicati
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: 7.2.3 Assignment Manager Tu
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?