1 / 14

Tracking Memory Performance of Siebel CTI Object managers

Tracking Memory Performance of Siebel CTI Object managers. With VA2™ for Siebel. Background. 7 production Siebel appservers, each 8 CPU 8gb physical memory ~3000 concurrent users Critical problem: >90% memory use requires reboots of all production appservers every 2 days

ghalib
Télécharger la présentation

Tracking Memory Performance of Siebel CTI Object managers

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Tracking Memory Performance of Siebel CTI Object managers With VA2™ for Siebel Recusive Technology LLC

  2. Background • 7 production Siebel appservers, each 8 CPU 8gb physical memory • ~3000 concurrent users • Critical problem: >90% memory use requires reboots of all production appservers every 2 days • Memory leak appears to be correlated with a code change in December 2005, however no historical info on memory use available • Manual methods not sufficient for identifying which processes are leaking memory • No historical information available to compare against current performance trends, in areas such as: • Number of Siebel tasks (users) • Performance of individual components • Memory and CPU use patterns per component and process • VA2 was used to track real time and historical information related to the memory leak problem Recusive Technology LLC

  3. Point in time: view of # of Siebel tasks per Siebel Appserver Realtime view for every Siebel appserver CTI Component: 440 Tasks 7 Processes Recusive Technology LLC

  4. VA2 - real time memory use per component eCommObj_CTI component is using about 2x physical and virtual memory than non CTI. About 5.3 GB of physical memory Other components have insignificant memory use Recusive Technology LLC

  5. Siebel appserver Prod7 process list Some CTI processes are using a huge amount of memory nearly 1 gig!! Others are using much less – why?? OS PID + Siebel component, shows which PID relates to each Siebel component Recusive Technology LLC

  6. CPU Use – CTI Obj Mgr using the most CPU time Recusive Technology LLC

  7. Historical: Statistics – used for historical reports 100% Customizable historical VA2 “Statistics”. Unlimited number of KPI (key performance indicators) available as Statistics Recusive Technology LLC

  8. Number of eCommOBJ_CTI Tasks Historical report on the number of CTI tasks running across all 7 Siebel servers. Consolidate view makes it easier to track total number across all appservers. Monday and Tuesday the 13th have higher number of tasks than previous days monitored. Recusive Technology LLC

  9. Drilldown into number of eCommOBJ_CTI Tasks (2) Drilling into Monday and Tuesday, the number of tasks reaches almost 4000 between 10am and 3PM then starts dropping. Number of tasks does not drop to 0, but 500 across all app servers- why?? Recusive Technology LLC Time

  10. Physical memory does not drop with # of tasks Physical memory was not released until a reboot Sunday night. There is an apparent memory leak, as the number of tasks from previous slide does not equal amount of physical memory used. And physical memory use continues to grow. Recusive Technology LLC

  11. Task report for 1 Appserver: Prod7 Number of tasks for Prod7 follows same trend as # of tasks for all appservers, meaning load balancing is working. Tops out at about 550 tasks. Recusive Technology LLC

  12. Physical memory use for Prod7 follows same trend For particular appserver Prod7, the physical memory use is the same as the larger pattern, of not releasing memory when number of tasks drop. The total amount of physical memory is very high, showing 5,500,000 KB or 5.5 GB of physical memory used for CTI components alone Recusive Technology LLC

  13. Virtual memory drops even less than physical with lower tasks Recusive Technology LLC

  14. Conclusions • Original problem of memory leak confirmed via monitoring – directly related to eCommObj_CTI Siebel components • After code changes (March 8 2006) and reboot (March 12 2006) , memory leak still apparent • Physical and virtual memory not being released with number of tasks dropping, causing a memory leak • Virtual Memory releases even less memory than physical • Number of CTI tasks never drops to zero even when there should be 0 users on the system • Siebel Service request should be started • Possibly engage Expert Services sizing review. • System running near capacity at all times – it could be that new load and not only code changes are now accelerating memory use • Use VA2 data to track trends / changes to the system Recusive Technology LLC

More Related