Hi Below are the main areas which we need to focus when we are doing a performance tuning. Hope this will help you.
Best practices for monitoring CPU consumption 1.Collect CPU usage data for each machine in the configuration. 2.Make sure less than 70% of the total CPU capacity is used on every system in the configuration. 3.Note which processes are consuming the majority of the CPU resources. 4.Note whether wait I/O time is a substantial component of CPU use. (This indicates that the I/O subsystem is not keeping up with demand.) Best practices for monitoring memory consumption 1.Make sure no system in the configuration is running out of physical memory and swapping. 2.Be aware of 64-bit and 32-bit limitations on both the OS and applications. 3.Track memory growth over time to identify any memory leaks. Best practices for tuning the mid tier 1.Use precaching to avoid high latency for first-time access to a form. 2.Set resource_check_interval to one day. 3.Set minimum heap size to 512 MB and maximum heap size to 1 GB. 4.Set pooling_max_total_connections to 2000. Best practices for tuning database (Oracle) servers 1.Use external storage to increase I/O bandwidth on the database server. 2.Use an appropriately sized System Global Area (SGA). 3.Set cursor_sharing to force in 9i and similar in 10g. 4.Use statspack (9i) or AWR (10g) reports to collect diagnostics. 5.If system is I/O bound or db_file_scattered_read events exist, consider whether highload SQL statements need tuning or additional indexes should be added. 6.Keep HASH_JOIN_ENABLED set to false (the default). Best practices for tuning the AR System server 1.Set thread count for fast and list to appropriate values. 2.Set NEXT_ID_BLOCK_SIZE to 10. 3.Use AR System server logging to obtain additional diagnostic information. 4.Set Max Entries Returned by GetList and Server Table Field Chunk Size to reduce the impact of queries with large return sets. Best practices for tuning the overall system 1.Survey each area of your system for possible tuning issues before making any changes. 2.Prioritize all changes by their likely impact on the identified problem. 3.Implement changes one at a time in a prioritized manner. 4.Quantitatively evaluate the impact of every change before considering whether another change should be made. Regards, Prasanth -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Jeff Jackson Sent: Monday, November 21, 2011 9:07 PM To: [email protected] Subject: Re: any experience or suggestions regarding improving performance of web client experience We are working on performance and tuning of our ITSM 7.6.03 implementation and am wondering if someone could point me in the right direction for the BMC bench mark document mentioned above. I have checked their knowledge base as well as the documentation for ITSM 7.6.03 and do not see it available for download. We would love to have this document to compare our system against. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" Think green - keep it on the screen. This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
