Presentation is loading. Please wait.

Presentation is loading. Please wait.

Maximizing Performance – Why is the disk subsystem crucial to console performance and what’s the best disk configuration. Extending Performance – How.

Similar presentations


Presentation on theme: "Maximizing Performance – Why is the disk subsystem crucial to console performance and what’s the best disk configuration. Extending Performance – How."— Presentation transcript:

1

2 Maximizing Performance – Why is the disk subsystem crucial to console performance and what’s the best disk configuration. Extending Performance – How to further improve console performance by implementing User Roles.

3 Native Performance (NP) Sequential IO Interactive Performance (IP) Random IO Track to Track Seek Time

4 Memory – Quantity Processor – Speed Network* – Quantity & Speed Bandwidth & Latency Disk - Multiple Variables Redundancy Quantity (Capacity) I/O Speed

5 Disk subsystems performance influenced by multiple variables: Storage tuning very complex due to many variables.

6 Minimum Disks: 4 Advantages: Combines read performance of RAID 0 w/ the fault-tolerance of RAID 1 Fault-Tolerance: Excellent Application: High performance applications requiring data protection and maximum read performance

7 SAN Optimized for Capacity. High Capacity Disks Reduces Spindle Count – Impedes I/O. Excess Capacity Shared Out. Cost per GB

8 5000 Agents / 7 Day Retention Primary Database = 170GB Single Disk: 15,000K RPM, SCSI/Fiber Channel 125-225 IO at 80% Greater than 100% - IO Requests Queued Thus Increasing Latency – Over Size IO Requirements Avg. Disk Sec/Read < 20ms / No Spikes* Max. Disk Reads/Sec = 6000 (Size for this, not the average)

9 6000 IO = 26 Disks (6000 IO / 225 IO) RAID 10 : 36 GB Disk = 936GB Raw / 468 Usable (36%) 72 GB Disk = 1872GB Raw / 936 Usable (18%) 144 GB Disk = 3744 Raw / 1872 Usable (9%) 300 GB Disk = 7800 Raw / 3900 Usable (04%) Extra space makes for a terrific parking lot, just minimize traffic.

10 What the customer needs to know: Required Database Size Avg. disk sec/read < 20 ms – maximum value Provide IO – Average & Maximum (n+1000) Information above necessary to design an appropriate disk subsystem. Let the SAN and Disk folks figure it out! Observed vs. Theoretical Capacity

11 Operations Console introduces load on OperationsManager database. Resource Intensive RMS influences performance too. All operations consoles connect to RMS. Unusually High Activity Disk Persistence Queue Large Number of Monitors Config Files – Large & Frequently Modified Solution: 64-Bit, Fast Disk & Physical Memory

12 Typical add more and more resources to get performance. Maximize what you have by reducing the overhead: Implement User Roles to control views. Why update objects not needed? Overhead. Considerably improves user experience in console. Deploy Web Console Limit Desktop Consoles Challenge – Requires Planning and Maintenance

13 RAID Calculator: http://www.dnfdefense.com/resources.asp/section/Re ading~Room/category/Technical~Information/options/ RAID~Calculator http://www.dnfdefense.com/resources.asp/section/Re ading~Room/category/Technical~Information/options/ RAID~Calculator OpsManJam Web Site: http://www.opsmanjam.com http://www.opsmanjam.com


Download ppt "Maximizing Performance – Why is the disk subsystem crucial to console performance and what’s the best disk configuration. Extending Performance – How."

Similar presentations


Ads by Google