Performance Tuning Siebel Software on the Sun Platform

More documents

Recommendations

Info

designed such that one thread of a <strong>Siebel</strong> OM services one user session or task. The ratio of threads or users/process is configured using the <strong>Siebel</strong> parameters: • MinMTServers • MaxMTServers • MaxTasks From several tests conducted it was found that on the Solaris platform with <strong>Siebel</strong> 7.5 the following users/OM ratios provided optimal performance: • Call Center – 80 users/OM • eChannel – 40 users/OM • eSales – 50 users/OM • eService – 60 users/OM As you can see, the optimal ratio of threads/process varies with the <strong>Siebel</strong> OM and the type of <strong>Siebel</strong> workload per user. MaxTasks divided by MaxMTServers determines the number of users/process. For example, for 300 users the setting would be MinMtServers=6, MaxMTServers=6, Maxtasks=300. This would direct <strong>Siebel</strong> to distribute the users across the 6 processes evenly, with 50 users on each. The notion of anonymous users must also be considered in this calculation, as discussed in the Call Center section, the eChannel section, and so on. The prstat –v or the top command shows how many threads or users or being serviced by a single multithreaded <strong>Siebel</strong> process. PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP 1880 pspp 504M 298M cpu14 28 0 0:00.00 10% siebmtshmw/69 1868 pspp 461M 125M sleep 58 0 0:00.00 2.5% siebmtshmw/61 1227 pspp 687M 516M cpu3 22 0 0:00.03 1.6% siebmtshmw/62 1751 pspp 630M 447M sleep 59 0 0:00.01 1.5% siebmtshmw/59 1789 pspp 594M 410M sleep 38 0 0:00.02 1.4% siebmtshmw/60 1246 pspp 681M 509M cpu20 38 0 0:00.03 1.2% siebmtshmw/62 A thread count of more than 50 threads per process is due to the fact that the count also includes some admin threads. If the MaxTasks/MTservers ratio is greater than 100, performance degrades in terms of longer transaction response times. The optimal users per process setting depends on the workload, that is, how busy each user is. 7.2.1 <strong>Tuning</strong> Call Center, Sales/Service, and eChannel <strong>Siebel</strong> Modules Call Center or sccobjmgr-specific information is presented here. Eighty users/process was found to be the optimal ratio. <strong>Performance</strong> <strong>Tuning</strong> <strong>Siebel</strong> <strong>Software</strong> on the Sun Platform Page 24
In the file $SIEBEL_ROOT/bin/enu/uagent.cfg: ● ● ● Set EnableCDA = FALSE to disable invoking CDA functionality. Set CommEnable = FALSE for Call Center, to disable downloading the CTI bar. Set CommConfigManager = FALSE. It should be noted that the preceding settings are required to be TRUE for scenarios where these functions are required. The benchmark setup required these settings to be disabled. To decide on the MaxTasks, MTservers, AnonUserPool settings, use the following example: Target No. of Users 4000 AnonUserPool 400 Buffer 200 Maxtasks 4600 MaxMTserver=MinMTserver 58 Table 7.2 If the target number of users is 4000, then AnonUserPool is 10% of 4000, or 400. Allow a 5% buffer, add them all together (4000+400+200=4600), and MaxTasks would be 4600. Since we want to run 80 users/process, the MaxMTserver value will be 4600/80=57.5 (rounded to 58). The AnonUserPool value is set in the eapps.cfg file on the <strong>Siebel</strong> Web Server Engine. If the load is distributed across multiple web server machines or instances, simply divide this number. In this example, if two web servers were being used, set AnonUserPool to 200 in each web server’s eapps.cfg file. Here is a snapshot of the file and the setting for Call Center: [/callcenter] AnonSessionTimeout = 360 GuestSessionTimeout = 60 SessionTimeout = 300 AnonUserPool = 200 ConnectString = siebel.tcpip.none.none://19.1.1.18:2320/siebel/SCCObjMgr Set the following env variables in the file $SIEBEL_HOME/siebsrvr/siebenv.csh or siebenv.sh: export SIEBEL_ASSERT_MODE=0 export SIEBEL_OSD_NLATCH = 7 * Maxtasks + 1000 export SIEBEL_OSD_LATCH = 1.2 * Maxtasks Set Asserts OFF by setting the environment variable SIEBEL_ASSERT_MODE=0. <strong>Performance</strong> <strong>Tuning</strong> <strong>Siebel</strong> <strong>Software</strong> on the Sun Platform Page 25
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: 7.1.3 The Solaris Kernel and TCP/IP
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

Create successful ePaper yourself

Delete template?

Save as template?