1 / 12

Understanding Scalability: Guidelines and Performance Insights for Optimal Load Management

Scalability is critical for predictable performance under varying loads. This guide outlines key aspects of scalability, including predictable responses, network constraints, and resource contention. It emphasizes the importance of testing and documentation while clarifying that guidelines are not guarantees. Factors such as network latency, CPU contention, and memory issues can significantly impact performance. Use this framework to assess scalability across different components, considering maximum capacity and performance benchmarks. Understand how to identify bottlenecks and improve system efficiency.

pravat
Download Presentation

Understanding Scalability: Guidelines and Performance Insights for Optimal Load Management

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. Scalability Overview Revised Dec 27 2005

  2. Scalability – What Is It • Predictable performance over a range of loads • Predictable does not equal good – just predictable • No growth preferred but linear response is acceptable • Just knowing performance hit for a load may be enough

  3. Scalability – We Document Guidelines • Guidelines are not a guarantee • Tests often ignore network (run on GB unconstrained) • Config, Bugs can confound any guidelines

  4. Scalability - Network • Network factors can slow any client server process down any amount desired • Scalability guidelines assume no network constraints • Factors: • End-to-end round trip time (satellite, excessive hops) • Bandwidth used up • Excessive errors • Config

  5. Scalability – Network – What to look for • Wide swings in CLI ping time • OS reported network load • Trace route

  6. Scalability – CPU Contention • Too much work running on one box • Task queuing, often with CPU close to 100% • Wide unexplained swings in response time

  7. Scalability – Memory Contention • Too much work running on one box • Excessive paging • Commit charge – time close to peak • Wide unexplained swings in response time

  8. Scalability – Resource “x” Contention • Too much work running on one box • Wide swings in response time, often unexplained

  9. Scalability – “max” Guidelines • Not a guarantee that you will like the performance • We test to determine breakpoints – max often is highest count that does not break • We report key performance values at max – you decide • See tests below max value • Guidelines are backed off max, but your “knee of curve” will vary

  10. Scalability • general – total objects*state changes/messages per second per/object • Deglitch chatter – do this as far down the foodchain as possible – define policy at top of foodchain, run the same policy everywhere to the extent possible – use attributes to guide policy

  11. Scalability • WorldView – number of maps, map complexity • CORE – total objects, state changes per second • Event – messages per second, # rules, % forwarded • DSM – total objects, polls per second • Agents – objects monitored, system internal poll rate, internal event rate • uDSM – machines per domain, replication to enterprise, reporting

  12. Scalability • DSM UAM – what items at enterprise level, number of domains, engines, sectors – network • DSM USD – admin and operational views for enterprise and local servers – network! • DSM USD – package size, number of packages, number of targets for a package, delivery windows • SD – Tickets/unit time; updates/unit time; # analysts; # clients connected at once

More Related