1 / 46

Server Consolidation Eric D. Ho Advisory Software Consultant BMC Software, Inc. March 20, 2002

Server Consolidation Eric D. Ho Advisory Software Consultant BMC Software, Inc. March 20, 2002. Objective. This presentation is designed to show the methodology by which server consolidation study can be achieved using PATROL Perform and Predict. Server Consolidation Advantages.

ull
Download Presentation

Server Consolidation Eric D. Ho Advisory Software Consultant BMC Software, Inc. March 20, 2002

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. Server Consolidation Eric D. HoAdvisory Software ConsultantBMC Software, Inc.March 20, 2002

  2. Objective • This presentation is designed to show the methodology by which server consolidation study can be achieved using PATROL Perform and Predict.

  3. Server Consolidation Advantages • Reduced total cost of ownership • Lower license cost for software • Improved system manageability • System backup and recovery • Software distribution • Reduce manpower requirements • Improve infrastructure technology • Replace older servers with newer technology • Faster processors will reduce workload response times and memory requirements

  4. Server Consolidation Challenges • Need to: • Measure current usage accurately • Capture the configuration details • Characterize workloads • Understand usage patterns • Predict the consolidation effect • Evaluate alternatives • Project growth

  5. Server Consolidation Risks • You don’t know where to start !! • Methodology, Process, Tools • Wrong Size - It does not fit !! • Oops! Career change? • It fits! But.. Performance stinks • Buy more…. Spend more! • It will take a long time !! • By the time you are done, the solution is obsolete.

  6. Server Consolidation Methodology • Six steps to Success • 1. Baseline current performance • Collect detailed performance data • 2. Characterize workload • System, utility, application, database, etc. • 3. Analyze resource usage level • Time Series Graphical Analysis • Peaks, batch windows, trends, growth pattern • Workloads profiles • 4. Combine systems for sizing • Server and Workload stacking • 5. Consolidation modeling • Resource contention analysis • Response time degradation analysis • Growth sensitivity analysis • 6. Validate recommendation

  7. 1 - Baseline Current Performance • Collect detailed performance metrics • System, IO, memory, process, user • 24x7 • Data collected every 10 seconds • Data logged every 15 minutes • 96 data records per day per server • Servers: as10, db02, db14, db15, and db25

  8. PATROL Data Collection Perform AGENT Proactive Planning Performance Check Workload Analysis Bottleneck Analysis Performance Reporting Predictive Analysis Capacity Planning Proactive Monitoring Thresholds Status/Alerts Detect Problems Recovery Actions Availability Problem Determination Problem Resolution PATROLAGENT PATROL Collector Kernel Data OS KM Daily Performance Files PATROL History File

  9. PATROL Perform & Predict Architecture NT UNIX Visualizer Reports Investigate UNIX and NT Real-Time Analysis TCP: 6767, 6768 PATROL Collect TCP: 10128 UNIX or NT Performance Model Predict Predictive Analysis Analyze Performance Analysis Performance Results Visualizer (Windows-based) VisualizerDatabase Graphical Analysis

  10. Systems Users Workloads Transactions 2. Workload Characterization • Logical Grouping • Who (users) • What (processes) • Where (servers) • Dynamic • Post Data Collection • Business Perspective • Application • Business Unit/Budget • Geographic

  11. Sample Workloads • Characterize workloads • Oracle (1 process = 1 transaction) • axciom (Oracle Instance MEMPWD) • f45 (Oracle Financials Form 45) • f60 (Oracle Financials Form 60) • ar25run • RGRAGR • PMSERVER • GL • tools (BMC, HP, etc.) • system • zzz (the rest of processes)

  12. 3 - Analyze Resource Usage Level • (A) Time Series Graphical Analysis • Peaks • Batch windows • Trends • Growth pattern • (B) Workload Analysis

  13. 3 - Analyze Resource Usage Level • (A) Time Series Graphical Analysis • Peaks • Batch windows • Trends • Growth pattern • (B) Workload Analysis

  14. Workload Analysis - as10 • as10 • HP N4000/06, 440 MHz • 14 GB memory • Peak Utilizations from 9am-10pm 1pm-2pm Major Workloads • dis4ws • f45 • f60

  15. Workload Analysis - db02 • db02 • HP V2500/20, • 440 MHz • 12 GB memory • Peak Utilization: 7am-7pm Major Workloads • Oracle • RGRARG

  16. Workload Analysis - db14 • db14 • Sun F6800/08, 750 MHz • 16 GB memory • Peak Utilization from 6pm-12am Major Workload • Oracle

  17. Workload Analysis - db15 • db15 • Sun F6800/08, 750 MHz • 16 GB memory • Peak Utilization from 1pm-7pm Major Workload • Oracle-Axciom

  18. Workload Analysis - db25 • db25 • Sun E4500/06, 440 MHz • 6 GB memory • Peak Utilization: • 5pm-10pm Major Workload • Oracle

  19. 4 - Combine Systems for Sizing • Server stacking • Combined as10 and db02 into 1 server • Change db02 from HP to Sun F6800 • Combined 2 database servers (db14 and db25) into 1 server • Workload stacking • Stack up all Oracle Instances • Check total capacity requirement • Use graphical visualization for quick check!

  20. Server Stacking • Stacked as10 and db02 servers • Total CPU requirement is about 1200% • 12 processors needed?

  21. Server Stacking • Stacked 3 database servers into 1 • Total CPU requirement is less than 1000% (10 processors) • IO issue? • Paging issue?

  22. Workload Stacking • Stacked all Oracle workloads into 1 server • Total CPU requirement is slightly over 800% (on 8 processors)

  23. 5 - Consolidation Modeling • Resource contention analysis • Combined as10 and db02 into 1 server • Change db02 from HP to Sun F6800/16 @750 MHz • Consolidate Workloads from db14 and db25 into db14 • Response time degradation analysis • Growth sensitivity analysis • Use 3/18/2002 14:00 to 15:00 as baseline interval Let’s see how PATROL Predict works…...

  24. Baseline Model: Mar-18-2002, 14:00 • Prepare the baseline model • Build a model for all nodes at peak utilization • Calibrate the models to ensure measured and calculated values are accurate.

  25. Baseline Analysis - Response Time • Note: • Response Time corresponded to transaction turnaround time • Relative Response Time was set to 1. Any “what-if” scenarios would change the Relative Response Time to reflect improvement or degradation

  26. Baseline Analysis - Utilization • Note: • This report shows the current workload breakdown of as10and db02 • We would “move” the application workloads from as10 to db02 as part of the server consolidation.

  27. Baseline Analysis • Note: • This report shows the current workload breakdown of db14, db15 and db25 • We would “move” the application workloads from db25 to db14 as part of the server consolidation.

  28. What-if Analyses • Growth Sensitivity Analysis • Server Sizing • Application Server • Database Server… • Application Sizing • Disaster Planning • Hardware Purchase Planning • Capacity Planning

  29. Consolidation Modeling #1 • Resource contention analysis • Combined as10 and db02 into 1 server • Change db02 from HP to Sun F6800/16 @ 750 MHz • Used 3/18/2002 14:00 to 15:00 as baseline interval

  30. What-if Modeling - Utilization • Note: • This report shows the workloads f45, f60, dis4ws and rw-procs were moved from as10 to db02. • Next, we would look at the relative response time changes.

  31. What-if Modeling - Response Time • Note: • This report shows the workloads f45, f60, dis4ws and rw-procs about 27% slower after they were moved. • The reason is that db02 has slower processor speed (25.27 specint95 per processor) than as10 (32.96 specint95), even though it has 20 processors versus 6 processors at as10. • Let’s see what happened when db02 is changed to a SUN F6800/16 machine.

  32. Note: • This report shows effect of the server upgraded. • The moved workloads are now 90% of the original time. • The oracle workload is now improved by 25%. • SUN F6800/16 at 750 Mhz is rated at 35.34 specint95 per processor)

  33. Consolidation Modeling #2 • Resource contention analysis • Consolidate Workloads from db14 and db25 into db14 • Used 3/18/2002 20:00 to 21:00 as baseline interval since db14 and db25 had higher utilization at night time.

  34. Workload Migration - Utilization • Note: • This report shows the Oracle@db25 moved to db14.

  35. Workload Migration - Response Time • Note: • This report shows the Oracle@db25 workload running at db14 received a 41% improvement on response time. • Original workloads on db14 were not affected by the moved Oracle workload

  36. 6 - Validate Recommendation • Create test environment • Observe results of initial implementation • Compare modeled results with “consolidated” measurement. • Re-model the combined systems to account for un-foreseen changes

  37. Server Consolidation Review • Six steps to Success • 1. Baseline current performance • Collect detailed performance data • 2. Characterize workload • System, utility, application, database, etc. • 3. Analyze resource usage level • Time Series Graphical Analysis • Peaks, batch windows, trends, growth pattern • Workloads profiles • 4. Combine systems for sizing • Server and Workload stacking • 5. Consolidation modeling • Resource contention analysis • Response time degradation analysis • Growth sensitivity analysis • 6. Validate recommendation

  38. STORAGE Consolidation Too? • BMC’s Application Centric Storage Management (ACSM) products can be leveraged to consolidate the storage side…

  39. PATROL Performance Management Summary • An established process • An integrated suite of products and services to manage mission critical client/server applications. • A proven methodology • Performance and capacity management across multiple platforms • Multi-functional • Performance Analysis • Daily Performance Visualization • Interactive Performance Prediction • High degree of process automation

  40. ROI’s • Ensure consistent approach to take on server consolidation projects • ROI: Reduce risks and costs • Enable IT staff to understand performance information and evaluate alternatives effectively • ROI: Better IT Performance/$ Ratio • Empower IT staff to plan for and justify expenditures with confidence • ROI: Timely hardware/software acquisitions

More Related