Performance Tuning Siebel Software on the Sun Platform

More documents

Recommendations

Info

8 <strong>Performance</strong> Tweaks with No Gains This section is most important as it sheds light on various myths of performance tuning. Sometimes a tunable that you think is sure to result in a performance gain, does not – but it ends up being counted as if it did. These are tunables that mostly help other applications in a different scenario or are default settings already in effect. This section lists out some of the tuning parameters that provided no gain when tested. Please note: These observations are specific to the workload, architecture, software versions, and so on used during the project at SUN ETC labs. The workload is described in Chapter 4. The outcome of certain tuneables may vary when implemented with a different workload on a different architecture/configuration. Changing the mainwin address MW_GMA_VADDR=0xc0000000 Changing this to other values did not seem to make a big difference to performance. This value is set in the siebenv file. Solaris Kernel Parameter stksize The default value for this is 16k, or 0x4000 on Sun4U (Ultra) architecture machines booted in 64 bit mode (which is always the default). Increasing this to 24k, 0x6000 by the below settings in /etc/system file did not provide any gains in performance during the tests. set rpcmod:svc_default_stksize=0x6000 set lwp_default_stksize=0x6000 <strong>Siebel</strong> Server Parameters 1. Recycle Factor. Enabling this did not provide any performance gains. Default is disabled. 2. SISSPERSISSCONN. This is the parameter that changes the multiplexing ratio between <strong>Siebel</strong> server and web server; its default value is 20. Varying this value did not result in any performance gains for the specific modules tested in this project with the PSPP standard workload (defined in Chapter 4). Resonate: Cache size -- RES_PERSIST_BLOCK_SIZE This is an environment variable which is set inside the resonate startup script. This was changed to as high as 240Kbytes and there was no difference in behavior. Sun Java System Web Server maxprocs This parameter, when changed from the default of 1, starts up more than one ns-httpd (web server process). No gain was measured with a value greater than 1. It was better to use a new web server instance. Database Connection Pooling with <strong>Siebel</strong> Server Components Enabling this for the server component batch workload caused performance to degrade such that server processes could not start. Some of the server component modules connect to the database using ODBC, which does not support connection pooling. <strong>Performance</strong> <strong>Tuning</strong> <strong>Siebel</strong> <strong>Software</strong> on the Sun Platform Page 56
Oracle Database Server 1. Larger than required sharedpoolsize. For a 10,000 <strong>Siebel</strong> user benchmark, a value of 400Mbytes was more than sufficient. Too large a value for sharedpoolsize wastes valuable database cache memory. 2. Large SGA. A larger than required SGA size is not going to improve performance, whereas too small an SGA size will degrade performance. 3. Large RBS. Being larger than required by an application would waste space in the database cache. It is better to make the application commit more often. <strong>Performance</strong> <strong>Tuning</strong> <strong>Siebel</strong> <strong>Software</strong> on the Sun Platform Page 57
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 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: use connection pooling, so you woul
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?