Managing Performance of Clustered Applications - 6350


Published on

1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Managing Performance of Clustered Applications - 6350

  1. 1. Managing Performance of Clustered Applications Yori Lavi Founder, Chief Product Officer [email_address]
  2. 2. Managing Performance of Clustered Applications ABSTRACT <ul><li>As more enterprises turn to J2EE to deliver their mission-critical applications over the Web, there is a greater reliance on clusters to provide mission-critical services to ensure maximum service availability and scalability. The challenges in clustering a J2EE application can be attributed to the very nature of distributed computing. Clusters promise to bring affordable mainframe-level computing power and reliability, using cost-effective servers. But clustering also introduces increased management complexity and amplifies the need for new transaction-level management approaches that can address the management complexity from a service delivery perspective. </li></ul>
  3. 3. Agenda <ul><li>Intro </li></ul><ul><li>Managing workloads – the performance perspective </li></ul><ul><li>Market trends </li></ul><ul><li>New clustering techniques create new challenges </li></ul><ul><li>Gap analysis: where existing tools fail </li></ul><ul><li>Moving forward – techniques to bridge the gap </li></ul><ul><li>Q&A </li></ul>
  4. 4. Managing workloads - the performance perspective <ul><li>Modern workloads – not your uncle’s mainframe workload </li></ul><ul><ul><li>Diversity </li></ul></ul><ul><ul><li>Variance </li></ul></ul><ul><ul><li>Rapid change </li></ul></ul><ul><li>Visibility – measure the right metrics </li></ul><ul><li>Active measures – control the right resources according to the right metrics </li></ul><ul><li>Anticipate deployment challenges based on combination of historical data and business projections </li></ul>
  5. 5. Market trends <ul><li>Application integration </li></ul><ul><ul><li>SOA, ESB, ad hoc custom integration </li></ul></ul><ul><ul><li>Method: </li></ul></ul><ul><ul><ul><li>Wrapping existing application with interfaces </li></ul></ul></ul><ul><ul><ul><li>Developing J2EE infrastructure tier between applications/services. </li></ul></ul></ul><ul><ul><ul><li>New flow management tools </li></ul></ul></ul><ul><ul><li>Benefits: </li></ul></ul><ul><ul><ul><li>Faster implementation of new business process. Better business flexibility </li></ul></ul></ul><ul><ul><ul><li>Focus on transaction level services (vs. application level services). </li></ul></ul></ul><ul><ul><li>New challenges: </li></ul></ul><ul><ul><ul><li>Increased need for visibility. (finer granularity: User, Transaction, resources per Trx/user/tier/machine…) </li></ul></ul></ul><ul><ul><ul><li>Increased need for (near) real-time control </li></ul></ul></ul><ul><ul><ul><li>More is riding on exact capacity planning </li></ul></ul></ul><ul><ul><ul><li>Higher need for understanding Cost of Transaction </li></ul></ul></ul><ul><ul><ul><li>Less control tools </li></ul></ul></ul>
  6. 6. Market trends <ul><li>Hardware consolidation </li></ul><ul><ul><li>Clusters, load balancing, virtualization </li></ul></ul><ul><ul><li>Method: </li></ul></ul><ul><ul><ul><li>Multiple, similarly configured tiers, operating together to server heterogeneous collection of users and applications </li></ul></ul></ul><ul><ul><li>Benefits: </li></ul></ul><ul><ul><ul><li>Higher availability </li></ul></ul></ul><ul><ul><ul><li>Lower TCO </li></ul></ul></ul><ul><ul><ul><li>Scalable architecture </li></ul></ul></ul><ul><ul><li>New challenges: </li></ul></ul><ul><ul><ul><li>Complexity is exponentially higher </li></ul></ul></ul><ul><ul><ul><li>Platform availability is higher, but service availability could be lower </li></ul></ul></ul><ul><ul><ul><li>Capacity planning tools are less effective </li></ul></ul></ul><ul><ul><ul><li>Lower visibility of transaction path and resource consumption makes problem isolation very difficult </li></ul></ul></ul><ul><ul><ul><li>Global configuration changes are not as effective as in a silo environment </li></ul></ul></ul>
  7. 7. New techniques create new challenges <ul><li>The business need is focused on service to user (Transaction). J2EE management tools focus on single ‘vertical’ tiers </li></ul><ul><li>ITIL require close tracking of service levels to the business, IT configuration management and IT procedure to manage both </li></ul><ul><li>In Silo-ed environment, over-provisioning and global parameter changes are effective </li></ul><ul><li>In clustered environment there are many more unpredictable variables </li></ul><ul><li>Number of components in a Silo are smaller than in integrated/cluster environment; therefore identification of changes and problems is more difficult in the new environment </li></ul>
  8. 8. Gap analysis: where existing tools fail <ul><li>Existing management tools disparately monitor either a user’s perspective or a single vertical tier in the stack/cluster or the cluster’s routing </li></ul><ul><li>Impact of a single tier problem was limited to a single silo </li></ul><ul><li>Context in a silo is more homogeneous </li></ul><ul><li>In Multi tiered, cluster environment: </li></ul><ul><ul><li>The context (who, what, where, when) is varied, masked and hard to follow </li></ul></ul><ul><ul><li>Any problem has a wide impact (multiple applications and users are integrated) </li></ul></ul><ul><ul><li>ID problem, business triage, problem isolation - needs to be near-real-time </li></ul></ul><ul><ul><li>Time to problem remediation is critical </li></ul></ul><ul><li>Existing management tools lack the context to provide the visibility and have no active remediation measures required in the new environments. </li></ul>
  9. 9. Moving forward – techniques to bridge the gap <ul><li>Requires new holistic approach that looks both at business context (WWWW – who, what, when, where) and physical context (Tiers, machines, resources, time line) </li></ul><ul><li>Implement holistic approach through the application life cycle: </li></ul><ul><ul><li>Pre deployment testing should look for SLA compliance per tier and per transaction </li></ul></ul><ul><ul><li>Capacity planning before deployment should have the real granular data: resource consumption per business service per tier </li></ul></ul><ul><ul><li>Cost of transaction should be known to the business well ahead of deployment </li></ul></ul><ul><ul><li>When deploying – need to monitor multiple levels. Both global (per transaction) SLA and per component (each leg a transaction perform on a each tier) </li></ul></ul><ul><ul><li>When deploying – need to monitor multi dimensional SLA (elapse time, CPU, IO, Memory, topology, calling ratio between tiers…) </li></ul></ul><ul><ul><li>When looking at a tier – look for resource consumption per transaction context, on a timeline </li></ul></ul><ul><ul><li>Once an SLA is breached, the NOC should be able to perform a quick business triage </li></ul></ul><ul><ul><li>Localizing the problem is quicker when the holistic approach is practiced </li></ul></ul><ul><ul><li>Utilizing active measures to remediate immediate problems </li></ul></ul><ul><ul><li>Employ techniques to control resource consumptions based on business policies </li></ul></ul>
  10. 10. Moving forward – techniques to bridge the gap <ul><li>Techniques </li></ul><ul><ul><li>Single repository infrastructure </li></ul></ul><ul><ul><li>Collection and aggregation platforms </li></ul></ul><ul><ul><li>Point collection techniques </li></ul></ul><ul><ul><ul><li>Instrumentation </li></ul></ul></ul><ul><ul><ul><li>Correlation </li></ul></ul></ul><ul><ul><ul><li>Tracking </li></ul></ul></ul><ul><ul><li>Consideration </li></ul></ul><ul><ul><ul><li>Low overhead, production grade </li></ul></ul></ul><ul><ul><ul><li>Quick Time To Value </li></ul></ul></ul><ul><ul><ul><li>Flexibility of monitoring and control tool. </li></ul></ul></ul><ul><li>Build, buy or both? </li></ul>
  11. 11. Business tracking of transactions fills the gap in SOA management solutions
  12. 12. Business tracking of transactions fills the gap in SOA management solutions (cont.)
  13. 13. <ul><li>[email_address] </li></ul><ul><li> </li></ul>Q&A OpTier is an innovator in Transaction Workload Management solutions that assure IT business service levels and optimize resources for the enterprise