Performance Tuning Siebel Software on the Sun Platform

More documents

Recommendations

Info

The following were the system resource settings from the failed machine: sdcv480s002:/export/home/sunperf/18306/siebsrvr/admin/%ulimit -a time(seconds) unlimited file(blocks) unlimited data(kbytes) unlimited stack(kbytes) 8192 coredump(blocks) unlimited nofiles(descriptors) 256 vmemory(kbytes) unlimited Even though the maximum size of the datasize or heap is reported as unlimited by the ulimit command above, the max limit is 2Gbytes by default on the Solaris OS. The upper limits seen by an application running on Solaris hardware can be achieved by using a simple C program that calls the getrlimit API from sys/resource.h. The following program prints the system limits for data, stack, and vmemory: #include #include #include #include #include static void showlimit(int resource, char* str) { struct rlimit lim; if (getrlimit(resource, &lim) != 0) { (void)printf("Couldn't retrieve %s limit\n", str); return; } (void)printf("Current/maximum %s limit is \t%lu / %lu\n", str, lim.rlim_cur, lim.rlim_max); } int main() { showlimit(RLIMIT_DATA, "data"); showlimit(RLIMIT_STACK, "stack"); showlimit(RLIMIT_VMEM, "vmem"); } return 0; Output from the C program on the failed machine is as follows: sdcv480s002:/export/siebsrvr/admin/%showlimits Current/maximum data limit is 2147483647 / 2147483647 Current/maximum stack limit is 8388608 / 2147483647 Current/maximum vmem limit is 2147483647 / 2147483647 From the output shown, it is clear that the processes were bound to a maximum data limit of 2Gbytes on an out-of-the-box Solaris system setup. This limitation is the reason for the failure of the siebsvc process as it tried to grow beyond 2Gbytes. Solution The solution is to increase the default system limit for datasize and reduce the stacksize. An increase in datasize creates more room for process address space and reduction of stacksize reduces the reserved stack space. Both these adjustments <strong>Performance</strong> <strong>Tuning</strong> <strong>Siebel</strong> <strong>Software</strong> on the Sun Platform Page 32
let a <strong>Siebel</strong> process use its process address space more efficiently, hence allowing the total <strong>Siebel</strong> process size to grow up to 4Gbytes (which is the upper limit for a 32-bit application). 1. What are the recommended values for data and stack sizes on Solaris OS while running the <strong>Siebel</strong> application? How does one change the limits of datasize and stacksize? Set the datasize to 4Gbytes (that is, the maximum address space allowed for a 32- bit process) and set the stacksize to any value
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: Investigating the Reason for the Fa
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

Performance Tuning Siebel Software on the Sun Platform

Create successful ePaper yourself

Delete template?

Save as template?