Professional Documents
Culture Documents
Agenda
Why Are We Here? Setting A Reasonable Goal It's a Cycle, Folks Understand Your Environment A word about add on products Take a Picture of Everyday Life Common Red Flags Thinking about SANs Dealing with the Virtual World A Quick Word About the Operating System
2 | 2012 IBM Corporation
Supply and Demand Throwing hardware at it no longer an option Stretching existing systems Making upgrades tactical Need numbers to justify actions Know what to look for
3 |
Changing demand New initiatives, new software, new users Most reasonable goal: Meet peak demand with (some) room to spare
4 |
You can't do this once and call it finished As system load changes, we must adjust and adapt
Remember that load can change in volume, footprint, complexity or all of the above
6 |
First Question: What does routine work look like? Make sure that your baseline includes at least one peak use time
Monday morning, 9 am?
Use this baseline to understand where your system pushes Identify potential pressure points
e.g. Peak use of particular facilities, but not yet in the danger zone
7 |
Authentication
Application
Storage
Firewall
Third-Party Component
8 |
9 |
Research In Motion's answer to mobile connectivity Does not run on your mail server but can have a huge impact NBES thread count can starve the hand held or overload the mail server
10 |
IBM Lotus Enterprise Integrator (LEI) / Domino Enterprise Connection Services (DECS)
Provide the interface to back-end database systems Can drive a high disk and network load
11 |
Disk I/O
Huge contributor to performance problems Disk Queue Length
# of pending requests (regardless of their size) Every OS vendor agrees disk queues longer than 2.0 indicate a bottleneck Look for both peak queue length and average queue length Usually expressed as a percentage Effects of high utilization are obvious High utilization can contribute to high queue lengths
Disk utilization
12 |
Paging
High paging can indicate RAM starvation Also increases disk activity can send you 'over the edge' with disk latency Set paging files to at least 1.5x RAM as baseline
Swapping
High swapping can indicate process thrashing Can be triggered by high volume of short-term activity (e.g. scripts, agents)
13 |
Looking for repeated spikes or high plateaus Easy for one process to effectively hang your system May need to go to per-process views to find culprit First cut match against known actions (agents, scripts, backups)
14 |
15 |
Regardless of vendor, you're still sharing one set of physical resources Still subject to interference from other virtual machines Still need to provision virtual machines as fully as real hardware Compare your performance to other virtual machines on the same host Be careful with moving virtual machines
Pay attention to overall application architecture Can lose fault-tolerance/failover
16 |
Be very, very careful Some patches can introduce problems all their own Use a test environment whenever possible Keep abreast of new patches Be sure to spot-check performance numbers after patch installation
17 |
18 |
In Conclusion...
No one right answer across systems or applications Performance tuning driven by your users, your data, your network It's a repeating cycle get used to it Partner with network/hardware teams for best effect
19 |
20 |
Legal disclaimer
IBM Corporation 2012. All Rights Reserved. The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBMs current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may change at any time at IBMs sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results. IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Quickr, Sametime, WebSphere, UC2, PartnerWorld and Lotusphere are trademarks of International Business Machines Corporation in the United States, other countries, or both. Unyte is a trademark of WebDialogs, Inc., in the United States, other countries, or both.
21 |