Software performance engineering is becoming increasingly important to businesses as they look to improve the non-functional performance of applications and get more out of IT investments. By leveraging performance engineering techniques, IT professionals can be indispensable in building and optimizing scalable systems. This
introductory course will teach you the essentials of software
performance engineering including :
• The performance challenges faced by Enterprise IT today
• What is software performance engineering (SPE)?
• Best practices for building scalable software systems
• The approaches to integrating SPE into IT project lifecycles
• Common frameworks for measuring application performance and service levels
• The impact of SPE on software developers, testers, capacity planes,
and other IT professionals
• Case studies from the finance, retail, and insurance industries
Instructor: Walter Kuketz, SVP and CTO, Collaborative Consulting
This training is sponsored by Correlsense, Collaborative Consulting,
and New Horizons
The document discusses the importance of non-functional requirements (NFRs) in software development. It notes that NFRs such as performance, reliability, and usability must be defined, tested, and validated throughout the development lifecycle. Ignoring NFRs can negatively impact the cost, timeline, and ultimate success of a project. The document provides examples of different types of NFRs and urges considering stakeholders' perspectives to prioritize the most important NFRs to test.
Dynatrace is an APM solution that provides deep visibility into application performance across complex, distributed environments. It uses PurePath technology to capture timing and code-level context for all transactions end-to-end. This allows Dynatrace to identify performance issues and their root causes faster than other tools. Dynatrace can monitor Apache Tomcat servers and provide metrics on JVM performance, database queries, requests, and more. It helps diagnose common issues like inefficient database access, microservice problems, and coding issues.
The Heuristic Test Strategy Model provides a framework for designing effective test strategies. It involves considering four key areas: 1) the project environment including resources, constraints, and other factors; 2) the product elements to be tested; 3) quality criteria such as functionality, usability, and security; and 4) appropriate test techniques to apply. Some common test techniques include functional testing, domain testing, stress testing, flow testing, and scenario testing.
The document discusses performance testing, including its goals, importance, types, prerequisites, management approaches, testing cycle, activities, common issues, typical fixes, challenges, and best practices. The key types of performance testing are load, stress, soak/endurance, volume/spike, scalability, and configuration testing. Performance testing aims to assess production readiness, compare platforms/configurations, evaluate against criteria, and discover poor performance. It is important for meeting user expectations and avoiding lost revenue.
Infographic: Importance of Performance TestingKiwiQA
Performance testing help to establish the scalability, speed, and stability of apps. It includes numerous testing types that simulate user scenarios and analyze app performance.
To learn more about performance testing, visit: https://www.kiwiqa.com/load-performance-testing.html
Analysis In Agile: It's More than Just User StoriesKent McDonald
A common question asked by teams adopting agile is "what does business analysis look like in agile?" The common answer is "writing user stories".
WRONG!
Okay, maybe not wrong, but certainly not the whole story (pardon the pun). Business analysis in agile is concerned with understanding the problem and possible solutions in order to ensure the team is building the right thing. User stories can be helpful, but are certainly not sufficient for doing that.
In this session, Kent McDonald describes how you can perform just enough business analysis to discover the right things to build. This includes how to really use value to decide what to build first, why process flows, data models, and mockups are still extremely helpful, and why the function of user stories is more important than their form.
Along the way, Kent shares examples from a system replacement project he is working on and suggests ways you can apply these techniques to your own projects.
Performance Engineering Case Study V1.0sambitgarnaik
This document discusses performance testing solutions and services offered by IonIdea. It provides an overview of IonIdea's performance testing tools for load testing, performance testing, and monitoring application and infrastructure performance. It also describes IonIdea's testing services such as performance testing, test automation consulting, and outsourced testing. Finally, it presents a case study example of how IonIdea used performance triage techniques including profiling and load testing to identify and address performance issues for an online banking application.
Introduction to Agile software testing - The 5th seminar in public seminar series from KMS Technology which have been delivering from 2011 in every two months
The document outlines a 5-step DevOps assessment and improvement process: 1) Intake and planning, 2) Discovery, 3) Roadmap development, 4) Piloting improvements, and 5) Wider rollout. It describes assessing an organization's DevOps capability maturity across people, processes, and tools. Deliverables include an assessment report, value stream map, deployment pipeline diagrams, and a 30-60-90 day continuous improvement plan. The key takeaway is that DevOps requires an open culture embracing Agile, Lean, and continuous feedback across stakeholders.
This document provides an agenda and overview for a performance testing training with JMeter. It begins with an introduction to performance testing, including the purpose and types of performance testing. It then covers getting started with JMeter, including installation, setup, and running JMeter. The remainder of the document outlines the content to be covered, including building test plans with JMeter, load and performance testing of websites, parameterization, adding assertions, and best practices. The goal is to teach participants how to use JMeter to perform various types of performance testing of applications and websites.
Agile software development is an iterative approach that emphasizes collaboration between self-organizing teams. It promotes adaptive planning, evolutionary development, and rapid response to change. Key characteristics include breaking work into small increments, short iterations of 1-4 weeks with full development cycles, cross-functional teams without hierarchy, and face-to-face communication. Agile differs from traditional methods by focusing more on collaboration and working software than documentation. Common challenges to adopting agile include getting individuals to work as cohesive teams and increasing transparency.
Documentation in the agile software development processFabian Kiss
Abandoning any documentation in agile software development is widespread due to a mistaken interpretation of the agile value "working software over comprehensive documentation". Aren't there any forms of documentation in practice which are actually agile?
Slides from a session presented by Fadi Stephan from Kaizenko at the 2019 Global Scrum Gathering in Austin, TX on 05/20/2019 DC. Also see the blog series on Agile Testing at https://www.kaizenko.com/agile-testing/
Abstract:
Many teams struggle with fitting in testing activities inside of a Sprint. They end up doing primarily development activities in a Sprint and push testing activities to run in dedicated testing Sprints following the coding Sprints or have a coding and testing Sprint running in parallel. However, in Scrum, the output of every Sprint is a potentially shippable product increment. This means the product increment should be well tested within the Sprint and ready to be delivered. Come to this presentation to learn how to tackle testing on an Agile team, what kind of tests to execute, what to automate and what not to automate, the different test responsibilities, and when to run which tests. Leave with a testing strategy that you can start applying the next day to gradually get a team to start testing from day 1 of the Sprint and deliver a true product increment at the end of each Sprint.
Enterprise QA and Application Testing ServicesCygnet Infotech
Cygnet’s innovation and insight-driven software testing services have paved way for numerous path-breaking software applications. Our meticulous approach towards application testing eliminates pesky bugs, reduces the time-to-market while optimizing the total-cost-of-ownership.
In this presentation which was delivered to testers in Manchester, I help would-be performance testers to get started in performance testing. Drawing on my experiences as a performance tester and test manager, I explain the principles of performance testing and highlight some of the pitfalls.
This document discusses testing and quality assurance for ERP modules. It provides an overview of the testing process roadmap, including establishing requirements and project scope, test planning, case development, different types of testing like unit, integration and user acceptance testing. It also outlines the personnel involved in testing like QA managers, analysts, writers. Metrics for test development and execution are also covered.
The concept of “shifting testing left” in the software development lifecycle is not new. Shifting testing from manual to automated and then upstream into engineering is a driving factor in DevOps and agile software development. However, Michael Nauman wonders why test automation, DevOps, and agile software development still frequently fail to deliver on their promises? Aligning and hardening your DevOps and test automation—along with streamlining your agile processes—is critical to your project. Michael shares how AutoCAD’s shifting testing left enabled improvements within their engineering team. Learn how the team increased engineering reliability and velocity, and forced process changes upstream into design and research all the way through to product support. Leave knowing why the concept of separation of concerns with regards to quality is as fundamental as the separation of code quality from product quality. Learn how the AutoCAD web team used process dogma and ruthless prioritization to combat metric idolatry and the host of other evils that hold teams back from fully realizing their potential and going beyond agile.
Cypress, Playwright, Selenium, or WebdriverIO? Let the Engineers Speak!Applitools
The document summarizes a discussion between several software engineers about test automation challenges and tools. It includes:
1) Names and social media handles of six engineers - Carter Capocaccia, Steve Hernandez, Jose Morales, Andrew Knight, Gleb Bahmutov, and Tally Barak.
2) A list of questions asked during the discussion about biggest challenges, favorite integrations, and aspects of other tools wished to be included in current projects.
3) Links shared by the panelists to resources on Cypress, Playwright, Selenium, WebdriverIO, visual testing and more.
Performance testing interview questions and answersGaruda Trainings
In software engineering, performance testing is in general testing performed to determine how a system performs in terms of responsiveness and stability under a particular workload. It can also serve to investigate, measure, validate or verify other quality attributes of the system, such as scalability, reliability and resource usage.
This document provides an overview of performance and load testing basics. It defines key terms like throughput, response time, and tuning. It explains the difference between performance, load, and stress testing. Performance testing is done to evaluate system speed, throughput, and utilization in comparison to other versions or products. Load testing exercises the system under heavy loads to identify problems, while stress testing tries to break the system. Performance testing should occur during design, development, and deployment phases to ensure system meets expectations under load. Key transactions like high frequency, mission critical, read, and update transactions should be tested. The testing process involves planning, recording test scripts, modifying scripts, executing tests, monitoring tests, and analyzing results.
The document summarizes a training session on performance testing using LoadRunner. It discusses planning load tests, the components of LoadRunner, creating scripts and scenarios, and enhancing scripts. Key points covered include the purpose of different types of tests, goals for performance testing, the workflow of a load test using LoadRunner, and developing scripts using Virtual User Generator.
Applying Performance Engineering Principles Throughout the SOA LifecycleRich Larrabee
This document discusses applying performance engineering principles throughout the service-oriented architecture (SOA) lifecycle. It recommends taking a risk-driven software development process that incorporates architectural views and methodologies from IBM Rational SOA Software and the IBM SOA Foundation Reference Architecture. The key aspects are taking both a "bottom up" simulation model and a "top-down" design approach to meet in the middle with a simulation model. This allows for early validation of design approaches through prototyped evaluation and validation of design patterns to ensure service and performance management throughout the full SOA lifecycle.
Bottlenecks limit application performance and can be caused by hardware, software, or network resources. Identifying bottlenecks in complex J2EE applications requires various tools. The process involves running load tests using diagnostic tools to identify bottleneck layers and components, then using profilers to debug problematic code. Monitoring application server heap usage and server resource consumption also helps identify bottlenecks.
This performance test plan outlines objectives to compare the responsiveness and resource utilization of a current production system and a new proposed production system. It defines the scope, dependencies, and risks. Tools like JMeter and PerfMon will be used to execute load tests on the systems and analyze results. Performance testing activities include installing tools, implementing tests, executing tests at typical loads, monitoring results, and delivering a test plan, results, and metrics.
Performance testing involves testing a system to determine how it performs under a particular workload. The document discusses various types of performance testing like load/capacity testing, stress testing, volume testing, endurance testing, and spike testing. It also discusses concepts like bottlenecks, prerequisites for performance testing, popular load testing tools like JMeter, and how to use key JMeter features for performance testing like adding users, HTTP requests, listeners, parameterization, correlation, assertions, and distributed testing.
Performance testing validates an application's responsiveness, stability, and other quality attributes under various workloads. It involves load testing, stress testing, endurance testing, spike testing, volume testing, availability testing, and scalability testing. The key parameters analyzed are response time, throughput, and memory utilization. Performance testing helps determine an application's speed, scalability, stability, and ability to handle changes in load and traffic over time.
Software team lead performance appraisalvictorluxman
This document provides materials and templates for performing a performance appraisal of a software team lead. It includes two pages of a sample performance appraisal form that evaluates a software team lead on various performance factors using ratings. It also includes sections on an employee's strengths and areas for improvement. The second part provides examples of performance review phrases related to attitude, creativity/innovation, and decision making that could be used in the appraisal.
Building High Performance Engineering Teams - Focus on People - Scrum Austral...Nicholas Muldoon
Twitter has grown from a handful of engineers to over a 1,000 in a few years. To be successful at such a scale requires finding the right people and making sure they are productive and solving valuable customer problems.
In this session Nicholas shares the techniques Twitter uses to hire amazing people, unleash their productivity, assess their performance, and improve the flock. Don't miss your chance to see how one of the fastest growing tech companies in Silicon Valley operates and retains the brightest talent.
The document discusses performance testing and how harnessing the cloud can help address challenges. It defines performance testing and outlines the typical process. Conducting performance tests on-premises can be challenging due to lab setup and maintenance, scaling users, and testing from different locations. These challenges can be overcome by using cloud-based performance testing services which provide flexible, scalable resources and pay-as-you-go models. Visual Studio Online is highlighted as one such cloud-based solution.
The document discusses various issues that can occur in multi-threaded applications and how thread dumps can help identify and diagnose them. It describes problems that can arise from I/O blocking, inefficient algorithms, lock contention, deadlocks, and non-thread-safe code. It provides examples like a HashMap causing 100% CPU usage. It also covers thread dump formats, tools for analyzing thread dumps, and questions that thread dumps may help answer about sporadic application behavior and performance problems.
Information Management is facing unprecedented upheaval due to one major force - Big Data. As quantities of information increase, it's possible to save vast amounts of data that in the past would have been discarded. Now, data is the raw material of exciting exercises in predictive analytics - and the results are game-changing for many businesses. Watch this joint webcast from Collaborative Consulting and IDG to learn how to launch a big data proof-of-concept at your organization.
Performance Engineering WebSphere Business Integration Case StudyRich Larrabee
A case study that illustrates the best practices for creating and managing a suite of shared services built upon the WebSphere Business Integration framework.
Georgia Tech: Performance Engineering - Queuing Theory and Predictive ModelingBrian Wilson
This is one lecture in a semester long course \'CS4803EPR\' I put together and taught at Georgia Tech, entitled "Enterprise Computing Performance Engineering"
----
Performance Engineering Overview - Part 2…
Queuing Theory Overview
Early life-cycle performance modeling
Simple Distributed System Model
Sequence Diagrams
This slide you give you the process of finding the performance bottleneck instantly.This process can be applied for any N tier architecture and any technology.
This document discusses how to bake quality into an agile scrum model. It covers quality driven by scrum practices like short iterations and frequent course corrections. It also discusses quality of requirements, architecture/design, code, verification/testing and maturing the definition of done. Automated testing, code reviews, continuous integration and refactoring are recommended to ensure code quality. Quality is baked in through quality user stories, engineering standards/best practices, exploratory testing and peer reviews.
The document discusses best practices for product design and development. It outlines key aspects of the process including identifying customer needs, establishing target specifications, concept generation, concept selection, concept testing, and setting final specifications. It also describes an evaluation framework that allows companies to compare their performance to industry benchmarks and best practices. The framework is used to develop an improvement plan by assessing a company's current situation, identifying gaps compared to best practices, and determining priorities based on business strategy and best practices.
This document discusses Behavior Driven Development (BDD), which is an agile software development methodology that focuses on defining and testing business requirements through executable specifications and acceptance criteria. The document covers the key concepts of BDD, including outside-in development, pull-based planning, and defining behavior through user stories and scenarios. It also discusses how BDD compares to other techniques like test-driven development and finite state machines. The overall goal of BDD is to facilitate collaboration between developers and business stakeholders to build the right product through living documentation of desired behaviors.
This is the presentation that I presented with Ruth Willenborg that provides a review of IBM's DevOps strategy as well as the roadmap for recently developed capabilities and future directions.
COMSYS is a large IT services and solutions company that provides Enterprise Resource Planning (ERP) consulting services. Their ERP practice has over 15 years of experience implementing SAP and JDEdwards solutions. They offer a range of services including project management, business process analysis, implementations, upgrades and more. COMSYS has over 250 ERP consultants and extensive relationships with SAP and other partners to deliver customized ERP solutions.
This document discusses how Visual Studio Team System can maximize ROI and drive IT governance through an integrated Application Lifecycle Management (ALM) solution. It provides concise summaries of key points, including how VSTS improves collaboration, ensures quality, integrates work frequently, and enables real-time decision making. IT governance is also discussed at a high level, focusing on compliance, metrics/reporting, and aligning IT with business needs. Examples are given of organizations seeing improvements in areas like productivity, quality, and cost reductions through an ALM approach.
The document provides an overview of Aspirea, an IT services company. It outlines Aspirea's areas of expertise including Microsoft technologies, other languages and frameworks, and domains like healthcare and ecommerce. It also describes Aspirea's product development approach, lifecycle capabilities, and services offered in areas like mobility and analytics. Examples of Aspirea's clients and a case study of a project for a mortgage service provider are also summarized.
The document outlines an iterative methodology for deploying Aras Innovator. It discusses dividing projects into manageable phases like inception, elaboration, construction, and transition. Each phase has objectives and milestones. The methodology emphasizes iterative design, managing requirements, continuous verification, and controlling changes. It provides tips for implementation like using visual prototypes, breaking work into components, and ensuring quality through user testing.
We had this presentation running on one of the screens in our booth at the April 4, 2013, Innotech Dallas/SharePoint TechFest. We have been excited by the developments in the latest release of Visual Studio and it's ability to work seamlessly with Microsoft's Azure.
This document discusses options for managing documents in SAP, including SAP DMS, Object Services, Business Documents, and Knowledge Management. It provides an overview of the capabilities of each tool and considerations for choosing the best one for a given purpose. The document also highlights how SAP DMS can be used effectively, demonstrating different interfaces and how other companies are leveraging it. It outlines the challenges engineering companies face with documentation and why a document management system is needed.
Nailing It Down: Detailed Design to Preserve the UX Visionjsokohl
Here are the key details for this page:
- Header displays reservation details like dates, room type, number of guests
- Breakdown of nightly rate, taxes, and total amount due per night
- Total for entire stay displayed prominently
- Links to terms, cancel policy displayed
- Large "Confirm Reservation" CTA button
- Footer with site links
Developer: Please implement the following:
- Pull reservation details like dates, room type, guests from booking API
- Calculate nightly rates, taxes, totals programmatically
- Display totals for full stay by multiplying nightly totals
- "Confirm Reservation" button triggers confirmation workflow
- Ensure all styling/layout matches existing
This document discusses application lifecycle management using Microsoft tools and processes. It covers planning and tracking projects, modeling applications, developing collaboratively, automating builds, and managing the application lifecycle from design through deployment. Resources for branching strategies, build customization, and more are also referenced.
Envisioning improving productivity and qaulity through better backlogs agi...Tatlock
This document summarizes a keynote presentation on improving productivity and quality through better product backlogs. The presentation discusses how problems with productivity, quality, and predictability often stem from issues with product backlogs, such as inconsistent story sizes and rework due to changing requirements. It advocates an approach called "Envisioning" to help plan requirements in a way that makes them more tangible, testable, and ensures the most important functionality is addressed. Large-scale adoption of Agile requires systemic organizational changes over 18-36 months, including establishing a common culture, vocabulary, and tools across distributed teams.
Key Considerations for a Successful Hyperion Planning ImplementationAlithya
The document provides an overview and recommendations for a successful Hyperion Planning implementation. It discusses key project phases, recommended build techniques including application definition, dimensionality, master data integration, building the planning model, and form and calculation development. It also covers tips for planning design including delineating plan types, defining dimensionality, integrating master data from various sources, and best practices for building forms to ensure performance.
This document introduces AppStory, a mobile app development company. It lists the managing partners and provides an agenda for the document. The agenda includes sections on the company background, AppStory's mobile services, and key service offerings like mobile strategy, integration, development, backend connectivity and cloud connectivity. The services are described briefly, with mobile strategy involving analyzing business needs and defining a roadmap, and development following an agile SCRUM methodology.
This document outlines an engagement model for developing a SaaS product. It involves several phases including product definition, design, development, launch, and ongoing maintenance. The product definition phase involves defining the market value, features, and operations. Product design determines the technology stack, architecture, and user experience. Development occurs in sprints, starting with sprint 0 for setup and sprint 1-N for building the product. The product then launches with testing and support. Ongoing maintenance and customer support continues after launch.
IBM Rational Quality Manager provides a centralized hub for collaborative test management across the software development lifecycle. It aims to mitigate business risk through stakeholder coordination and enforceable process workflows, improve operational efficiency via test automation and lab management, and make confident decisions with effortless reporting and metrics. The solution emphasizes collaboration, automation, and reporting to govern software quality.
Session #1: Development Practices And The Microsoft ApproachSteve Lange
This document discusses Microsoft's approach to development best practices, which focuses on collaboration, managing team workflow, driving predictability, ensuring quality early and often, and integrating work frequently. It describes how Microsoft's Visual Studio Team System provides tools to help with collaboration, work tracking, process guidance, testing, version control, and reporting to support development teams.
SAP CVN Supply Network Planning - Supply Planning Engine SelectionPlan4Demand
This document summarizes a presentation on supply chain planning given by Plan4Demand Solutions. The presentation covered challenges with supply planning, tools for optimization, and questions. It discussed Plan4Demand's consulting services in supply chain planning areas like demand forecasting and inventory optimization. The presentation also covered supply planning engine selection, change management, and challenges with aligning supply network planning results to master data.
Similar to An Introduction to Software Performance Engineering (20)
Unify Citrix & Back End Application Performance Data Presented by CorrelsenseCorrelsense
Rich client and Citrix applications are used widely in the enterprise environments, however one of the biggest blind spots of enterprises when it comes to providing visibility of any application, seems to be the delivery of services via citrix
Secrets to Seeing it All; Enterpise Application Performance Management Correlsense
This document discusses enterprise application performance monitoring (APM). It describes how APM can measure real user experience across endpoints, track individual transactions across systems, and isolate sporadic problems. The goal is to provide alerts, analytics dashboards and reports to various teams to help address performance issues.
Correlsense Enterprise APM vs Traditional Infographic Correlsense
Fascinating infographic that takes a look at Enterprise Application Performance Monitoring ver Traditional.
Enterprise businesses use new, legacy, and commercial
applications written in multiple programming languages. They may touch middleware components and reach end-users on browsers, rich clients, and mobile devices.
While traditional APM Traditional APM (or developer APM) products are designed to monitor vertical technology stacks like Java, .NET or PHP, on browsers and mobile devices. They provide strong technology support inside each stack, good deep dive capabilities, and are often used as part of new application development.
Best Practices for Managing and Monitoring WebSphere Message BrokerCorrelsense
WebSphere Message Broker serves as a transactional backbone for many IT organizations yet introduces complexity around integrating, managing and monitoring messaging-based solutions. This results in lost message flows and stalled transactions. Join Correlsense for an online seminar which teaches holistic management and monitoring solutions for gaining visibility into and taking control of WMB. We discuss:
-How to identify key implementation and management challenges for WMB 6, 7 or 8
-A new approach to locating stalled transactions, understanding application dependencies and monitoring message flows
-Real world case studies and a live demo that illustrate ways to gain deeper visibility into your WebSphere Message Broker
Strategies for Securing Availability and Optimizing Application Performance i...Correlsense
This document discusses strategies for securing availability and optimizing application performance in the cloud using Red Hat OpenShift and Correlsense. OpenShift is a Platform as a Service (PaaS) offering from Red Hat that provides a cloud application platform. Correlsense provides management and monitoring tools that integrate with OpenShift to help operations and development teams optimize application performance. The presentation covers OpenShift features, how it automates application deployment, and how Correlsense helps with user experience monitoring, code diagnostics, dependency mapping, capacity planning, and auto-scaling of applications on OpenShift. It concludes with a demonstration of Correlsense's capabilities.
Preventing the Next Deployment Issue with Continuous Performance Testing and ...Correlsense
Traditionally, identifying and remedying performance problems resulting from application deployments has been a slow, reactive process. Tools exist which report on application changes and problems after they occur, but how do you prevent your next performance issues before they even begins?
Join Correlsense and dbMaestro for an online seminar outlining the crucial strategies for continuous performance testing and monitoring. We will discuss:
-Limitations of traditional strategies for application deployments
-Best practices for eliminating the risks of application changes
-Solutions for proactive application performance monitoring and database change management
5 APM and Capacity Planning Imperatives for a Virtualized WorldCorrelsense
The proliferation of virtualized applications has greatly increased the complexity of capacity planning and performance management. Monitoring and forecasting CPU utilization is no longer enough. IT operations and capacity planners now must understand and optimize their applications and infrastructure from the end user to the data center.
Join Correlsense and Metron-Athene for an online seminar which will explore key performance management and capacity planning strategies for a virtualized world. We will discuss:
What you need to know about capacity management when operating in both physical and virtual environments
How performance monitoring in virtual environments relates to your capacity management goals
What is unique about capacity and performance management for virtualized applications
New Approaches to Faster Oracle Forms System PerformanceCorrelsense
Are your end-users complaining that Forms is slow? Ever wonder what the source of the problem is? Want to learn what are the fastest, most effective strategies to improve overall performance and end user experience?
Join us for a webinar where we will showcase best practices for application support engineers, application owners, QA engineers, Oracle Forms developers and EBS Integrators. Topics include:
Minimizing start up times and resource requirements
Improving speed of Forms rendering
Gaining visibility into the potential source of bottlenecks in Oracle components
Speakers: Mia Urman, CEO of OraPlayer Ltd. and Frank Days, VP of Marketing, Correlsense
The Essentials of Mobile App Performance Testing and MonitoringCorrelsense
Complexity across mobile carriers, locations and operating systems has made building mobile apps and monitoring their end user performance time consuming and expensive. The importance of testing mobile apps on iOS, Android and Windows Phone is increasing as more users embrace these devices. Join Correlsense and uTest for an online seminar which will teach you the steps to successful mobile application testing and performance management. We will discuss:
- The proliferation of mobile devices and the technical challenges they bring to end user experience monitoring
- Ways to prepare mobile applications for peak usage periods with the right load and performance testing techniques
- Tips and techniques for gaining visibility into the performance of mobile applications with the right monitoring tools
We will conclude with a discussion of the Correlsense and uTest solutions.
Five Keys for Performance Management of Oracle Forms and E-Business SuiteCorrelsense
This document discusses five keys to managing the performance of Oracle Forms and Oracle E-Business Suite applications. It outlines the challenges of monitoring complex multi-tier Forms architectures and the need to track individual user sessions across all components. The five keys are: 1) track all requests through all tiers, 2) manage user experience with meaningful transaction names, 3) understand how components interact, 4) use performance analytics, and 5) keep stakeholders aware. It then discusses limitations of existing monitoring solutions and how SharePath addresses these limitations by providing end-to-end transaction visibility across all layers without requiring code changes.
Best Practices for Managing SaaS ApplicationsCorrelsense
The document outlines best practices for managing SaaS applications. It begins with facts about the growing SaaS market and adoption trends. It then discusses challenges of SaaS for large organizations and the changing role of IT. The main section covers best practices such as defining requirements upfront, planning for integration, security, compliance and ongoing support needs. It emphasizes the importance of tools to measure performance across applications, geographies and over time to effectively manage SaaS. The presentation concludes with a question and answer segment.
The increasing adoption of DevOps principles has led to greater integration between software development (both application and software engineering) and IT operations (both systems administration and infrastructure). In this online seminar, we will explore the DevOps approaches
An Integrated Approach to ITIL Aligned Capacity ManagementCorrelsense
A brief overview of ITIL Capacity Management. The need for both component data and transaction data to do effective Capacity Management. Monitor your business transactions. Component data, business data and a framework for Capacity Management reporting, analysis, and planning. An integrated solution for Capacity Management
New approaches to managing complex applicationsCorrelsense
The proliferation of multi-platform, web-enabled, cloud-based applications within an increasingly complex IT infrastructure creates a host of new management challenges. As your transactions move between new distributed systems and legacy mainframes components your existing approach to application monitoring might be missing important performance issues.
In this informative presentation, we discuss:
- Strategies for managing these increasingly complex applications
- New approaches to managing service levels - from the browser to the mainframe
- Innovative ways to gain complete visibility into end-to-end user experience and eliminate all application performance blind-spots
This document outlines an agenda for a presentation on measuring, managing, and improving service levels. The presentation will discuss seven best practices for doing so, including looking at deltas over time, being proactive about service level agreements, going beyond just load testing, examining your live topology, and monitoring all components of transactions. It will also include a demonstration of the SharePath tool for monitoring service levels and time for questions.
EMA - Measuring the User Experience in the CloudCorrelsense
Cloud computing brings with it many benefits, especially lower IT costs and increased flexibility. However, the dynamic, hybrid nature of Cloud environments require enterprises to re-think their existing IT management processes and tools. Applications that perform poorly and fail to meet service levels — whether on premise or in the Cloud — can cause users to churn and revenues to drop.
Join EMA Research Director Julie Craig and Correlsense CEO Oren Elias for this Webinar that will highlight ways to measure how end users experience your business applications, as well as identify which approaches are likely candidates for a long-term strategy.
Attendees will learn:
How end-user response times are impacted by components and new changes that are introduced in the IT environment
The 3 tips for managing Cloud-based applications
The "secret sauce" for reliable end user monitoring, based on customer case studies that will be presented
Show Me the Money: Connecting Performance Engineering to Real Business ResultsCorrelsense
Performance testing and optimization are often neglected parts of enterprise application roll out and upgrade initiatives.
The challenge for many IT managers is communicating the value of IT performance projects to business stakeholders who would benefit the most.
An interactive discussion with Walter Kuketz, CTO of Collaborative Consulting where he shares:
- How to align key business drivers with your performance engineering projects
- Ways to bridge the IT-business stakeholder communication gap
- A new approach to model business transactions and their IT dependencies
Host: Frank Days
Title: VP of Marketing, Correlsense
How Social Media Hackers Help You to See Your Wife's Message.pdfHackersList
In the modern digital era, social media platforms have become integral to our daily lives. These platforms, including Facebook, Instagram, WhatsApp, and Snapchat, offer countless ways to connect, share, and communicate.
Sustainability requires ingenuity and stewardship. Did you know Pigging Solutions pigging systems help you achieve your sustainable manufacturing goals AND provide rapid return on investment.
How? Our systems recover over 99% of product in transfer piping. Recovering trapped product from transfer lines that would otherwise become flush-waste, means you can increase batch yields and eliminate flush waste. From raw materials to finished product, if you can pump it, we can pig it.
How RPA Help in the Transportation and Logistics Industry.pptxSynapseIndia
Revolutionize your transportation processes with our cutting-edge RPA software. Automate repetitive tasks, reduce costs, and enhance efficiency in the logistics sector with our advanced solutions.
Scaling Connections in PostgreSQL Postgres Bangalore(PGBLR) Meetup-2 - MydbopsMydbops
This presentation, delivered at the Postgres Bangalore (PGBLR) Meetup-2 on June 29th, 2024, dives deep into connection pooling for PostgreSQL databases. Aakash M, a PostgreSQL Tech Lead at Mydbops, explores the challenges of managing numerous connections and explains how connection pooling optimizes performance and resource utilization.
Key Takeaways:
* Understand why connection pooling is essential for high-traffic applications
* Explore various connection poolers available for PostgreSQL, including pgbouncer
* Learn the configuration options and functionalities of pgbouncer
* Discover best practices for monitoring and troubleshooting connection pooling setups
* Gain insights into real-world use cases and considerations for production environments
This presentation is ideal for:
* Database administrators (DBAs)
* Developers working with PostgreSQL
* DevOps engineers
* Anyone interested in optimizing PostgreSQL performance
Contact info@mydbops.com for PostgreSQL Managed, Consulting and Remote DBA Services
Best Programming Language for Civil EngineersAwais Yaseen
The integration of programming into civil engineering is transforming the industry. We can design complex infrastructure projects and analyse large datasets. Imagine revolutionizing the way we build our cities and infrastructure, all by the power of coding. Programming skills are no longer just a bonus—they’re a game changer in this era.
Technology is revolutionizing civil engineering by integrating advanced tools and techniques. Programming allows for the automation of repetitive tasks, enhancing the accuracy of designs, simulations, and analyses. With the advent of artificial intelligence and machine learning, engineers can now predict structural behaviors under various conditions, optimize material usage, and improve project planning.
Fluttercon 2024: Showing that you care about security - OpenSSF Scorecards fo...Chris Swan
Have you noticed the OpenSSF Scorecard badges on the official Dart and Flutter repos? It's Google's way of showing that they care about security. Practices such as pinning dependencies, branch protection, required reviews, continuous integration tests etc. are measured to provide a score and accompanying badge.
You can do the same for your projects, and this presentation will show you how, with an emphasis on the unique challenges that come up when working with Dart and Flutter.
The session will provide a walkthrough of the steps involved in securing a first repository, and then what it takes to repeat that process across an organization with multiple repos. It will also look at the ongoing maintenance involved once scorecards have been implemented, and how aspects of that maintenance can be better automated to minimize toil.
Kief Morris rethinks the infrastructure code delivery lifecycle, advocating for a shift towards composable infrastructure systems. We should shift to designing around deployable components rather than code modules, use more useful levels of abstraction, and drive design and deployment from applications rather than bottom-up, monolithic architecture and delivery.
The Rise of Supernetwork Data Intensive ComputingLarry Smarr
Invited Remote Lecture to SC21
The International Conference for High Performance Computing, Networking, Storage, and Analysis
St. Louis, Missouri
November 18, 2021
Paradigm Shifts in User Modeling: A Journey from Historical Foundations to Em...Erasmo Purificato
Slide of the tutorial entitled "Paradigm Shifts in User Modeling: A Journey from Historical Foundations to Emerging Trends" held at UMAP'24: 32nd ACM Conference on User Modeling, Adaptation and Personalization (July 1, 2024 | Cagliari, Italy)
Are you interested in dipping your toes in the cloud native observability waters, but as an engineer you are not sure where to get started with tracing problems through your microservices and application landscapes on Kubernetes? Then this is the session for you, where we take you on your first steps in an active open-source project that offers a buffet of languages, challenges, and opportunities for getting started with telemetry data.
The project is called openTelemetry, but before diving into the specifics, we’ll start with de-mystifying key concepts and terms such as observability, telemetry, instrumentation, cardinality, percentile to lay a foundation. After understanding the nuts and bolts of observability and distributed traces, we’ll explore the openTelemetry community; its Special Interest Groups (SIGs), repositories, and how to become not only an end-user, but possibly a contributor.We will wrap up with an overview of the components in this project, such as the Collector, the OpenTelemetry protocol (OTLP), its APIs, and its SDKs.
Attendees will leave with an understanding of key observability concepts, become grounded in distributed tracing terminology, be aware of the components of openTelemetry, and know how to take their first steps to an open-source contribution!
Key Takeaways: Open source, vendor neutral instrumentation is an exciting new reality as the industry standardizes on openTelemetry for observability. OpenTelemetry is on a mission to enable effective observability by making high-quality, portable telemetry ubiquitous. The world of observability and monitoring today has a steep learning curve and in order to achieve ubiquity, the project would benefit from growing our contributor community.
Comparison Table of DiskWarrior Alternatives.pdfAndrey Yasko
To help you choose the best DiskWarrior alternative, we've compiled a comparison table summarizing the features, pros, cons, and pricing of six alternatives.
Details of description part II: Describing images in practice - Tech Forum 2024BookNet Canada
This presentation explores the practical application of image description techniques. Familiar guidelines will be demonstrated in practice, and descriptions will be developed “live”! If you have learned a lot about the theory of image description techniques but want to feel more confident putting them into practice, this is the presentation for you. There will be useful, actionable information for everyone, whether you are working with authors, colleagues, alone, or leveraging AI as a collaborator.
Link to presentation recording and transcript: https://bnctechforum.ca/sessions/details-of-description-part-ii-describing-images-in-practice/
Presented by BookNet Canada on June 25, 2024, with support from the Department of Canadian Heritage.
An invited talk given by Mark Billinghurst on Research Directions for Cross Reality Interfaces. This was given on July 2nd 2024 as part of the 2024 Summer School on Cross Reality in Hagenberg, Austria (July 1st - 7th)
Advanced Techniques for Cyber Security Analysis and Anomaly DetectionBert Blevins
Cybersecurity is a major concern in today's connected digital world. Threats to organizations are constantly evolving and have the potential to compromise sensitive information, disrupt operations, and lead to significant financial losses. Traditional cybersecurity techniques often fall short against modern attackers. Therefore, advanced techniques for cyber security analysis and anomaly detection are essential for protecting digital assets. This blog explores these cutting-edge methods, providing a comprehensive overview of their application and importance.
Mitigating the Impact of State Management in Cloud Stream Processing SystemsScyllaDB
Stream processing is a crucial component of modern data infrastructure, but constructing an efficient and scalable stream processing system can be challenging. Decoupling compute and storage architecture has emerged as an effective solution to these challenges, but it can introduce high latency issues, especially when dealing with complex continuous queries that necessitate managing extra-large internal states.
In this talk, we focus on addressing the high latency issues associated with S3 storage in stream processing systems that employ a decoupled compute and storage architecture. We delve into the root causes of latency in this context and explore various techniques to minimize the impact of S3 latency on stream processing performance. Our proposed approach is to implement a tiered storage mechanism that leverages a blend of high-performance and low-cost storage tiers to reduce data movement between the compute and storage layers while maintaining efficient processing.
Throughout the talk, we will present experimental results that demonstrate the effectiveness of our approach in mitigating the impact of S3 latency on stream processing. By the end of the talk, attendees will have gained insights into how to optimize their stream processing systems for reduced latency and improved cost-efficiency.
2. Housekeeping
Presentation will last 45 Submit questions via the Slides will be made
minutes chat window available
2
2012 Collaborative Consulting
3. Purpose of today’s webinar
Review the current challenges of being a performance engineer
Overview of the five knowledge areas of Software performance engineering body of knowldge
Where to inject PE tasks and activities into the SDLC to build more performant applications
Overview of application performance management (end-to-end user experience)
Roles and career path overview
Case study – 10X event
3
2012 Collaborative Consulting
4. Performance engineering challenges today
Highly • Complex and tangled system of systems
distributed • Distributed Infrastructure
apps • Distributed production operations
• Performance engineering and testing
Distributed
• Architecture and development
teams
• Business
Evolving & • Mobile devices
changing • Third party services
application • SaaS products
architectures • Cloud
Changing • Driven by mobile anywhere
usage
• Flash traffic events
patterns
4
2012 Collaborative Consulting
5. Performance engineering challenges
User
Enterprise Budget Team skills
experience
• Release • User populations • Constant cost • Performance
schedules, mont are exploding and budget organization;
hly, quarterly pressure skillsets, multi
• Web site disciplined,
• Project based performance • Maintaining a communication,
directly impacts meaningful split team
revenue performance lab
(production-like) • Training and
career paths
5
2012 Collaborative Consulting
6. No clear standards in the market for PE
Test automation technician
Capacity planner
?
Performance tester
?
? Performance Engineer
Performance analyst
?
Performance Architect
?
Benchmarks
?
Troubleshooting
Performance Data engineer
?
6
2012 Collaborative Consulting
7. Goal of the SPE Body of Knowledge
Define the profession of performance
Define profession engineering
Establish Body of Establish a body of knowledge for
Knowldge performance engineering
Establish Establish a common language for roles,
common responsibilities, and practice areas using
language the form of Knowledge Areas
Define Define the competencies shared across
competencies the knowledge areas
Capture common Capture common techniques for sharing
techniques across the industry
7
2012 Collaborative Consulting
8. The SPE Body of Knowledge
Enterprise Software Performance Engineering
Planning, coordination, information sharing, and control
Knowledge areas
Performance
validation and testing Problem
Application
SDLC & (PVT) detection
performance
architecture and
management
(SA) Capacity planning (APM)
resolution
(PDR)
(CP)
Underlying competencies and roles for delivering
Techniques supporting the knowledge areas
8
2012 Collaborative Consulting
9. The Enterprise PE team: There must be a practice leader
A shared service and clearing house for all performance, scalability and
capacity planning information. Transforms performance information to
business knowledge and advantage.
Communicates across the teams to share information
For instance, the production workload and the
Operations PT performance test workload – are they in sync?
Architecture and Make sure the architecture team knows how the
production new release, or newest build behave in production.
The business risks are clearly identified and
Business direction communicated.
Can provide performance guidelines to the
Development teams developers, must influence the unit testing process.
9
2012 Collaborative Consulting
10. Information sharing across the knowledge areas
Enterprise PE
Capacity
planning and planning Triage
monitoring
SPE impacts Architects,
Results,
Developers, testing, and
Forecast Workload operations
Workload scalability
NFR’s Performance User Exp
Volumetrics, validation, Workload
Utilization
workload testing
SDLC, Results
Architecture Observations APM
, NFR
Growth plans
Workload
NFR’s
10
2012 Collaborative Consulting
11. PE: Knowledge areas
SA PVT CP APM PDR
Software development Performance testing and Capacity planning Application performance Problem detection and
lifecycle and architecture validation management resolution
11
2012 Collaborative Consulting
12. PE: Software development lifecycle and architecture
SA PVT CP APM PDR
Software development Performance testing and Capacity planning Application performance Problem detection and
lifecycle and architecture validation management resolution
12
2012 Collaborative Consulting
13. PE: SA (software development lifecycle)
Waterfall methodologies
Functional Performance
Define Design Develop Deploy
test test
Need to plan for Build code to performance
performance testing requirements
Define
Deploy Agile Design
methods
Test Build
Can a system be designed to support 10 TPS and 1 second response time work @ 100 TPS and 1 second?
13
2012 Collaborative Consulting
14. SDLC: Define and design
Define Design
1. Project risk scorecard 1. Technology Architecture validated
- Key business transactions to the performance Usage
identified Scenarios. How will it achieve the
- Workflow constraints key performance requirements?
Sub-second
- SLA’s and penalties response time. Define the scalability approach.
Flash marketing
2. Workload model and usage event. 2. Scalability to support flash events
scenarios
3. Environments: include any
3. Business volumes with peak
required changes to develop and
factors
test the performance usage
4. Business performance scenarios.
requirements
Communication to your downstream processes and people
Prepare to deal with flash events
Design to avoid flash events
(they are expensive. E.g. Work with business why does the outbound email
have to send email to all xM customers at the same time
14
2012 Collaborative Consulting
15. SDLC: Develop and functional testing
Functions are tested. Performance needs to be analyzed.
Develop Functional test
• The functions are mapped to software • Verify business functions and key
components. The performance req’s are performance functions.
assigned to the components.
• Verify the key performance workflows
• Unit testing for early validation of the and functions.
performance req’s for the software
components. Response time • Define and execute micro-performance
measurements. testing in the QA process.
• Integration testing include micro- • Produce report on for each key
performance testing of key functions. performance Usage Scenario with
Code review of the key performance response time and throughput.
functions.
• Enhance unit and integration test for
early validation of key performance
functions
Greatest impact on performance and scalability, but you must know the goals.
Communication to your downstream processes and people
15
2012 Collaborative Consulting
16. Performance budgets
Do your developers know how much time they have for their piece of the transaction?
Code runs
everywhere.
SERVER
WEB APP SVR
PROXY
MQ/ESB
LDAP CORBA
DCOM
Respond to the user
in 2 seconds. Web
Services
Datacenter
16
2012 Collaborative Consulting
17. PE: Performance testing and validation
SA PVT CP APM PDR
Software development Performance testing and Capacity planning Application performance Problem detection and
lifecycle and architecture validation management resolution
17
2012 Collaborative Consulting
18. PE: PTV (performance testing and validation)
What is changing? Where does it need to be validated? What (all) is being measured?
The project: Why are we testing and what are the success criteria?
Prerequisites:
Business goals and non-functional requirements are defined
Workload and scenarios defined
Environment defined (where are we testing)
Application in a stable state
Configuration management and release management ready
Core performance team identified
Supporting team committed
18
2012 Collaborative Consulting
19. Organization: Performance team value
You still need to explain to the rest of the organization what you do
Business and Early involvement
application area with the applications Test execution Environment
knowledge team
• Deep understanding of • Performance engineers • Well-understood • Testing environment is
the application being involved in design workload model and a close approximation
tested sessions characterization of production, including
database size
• Deep understanding of • Understand the nature • All components in the
the technical of the data required for test are monitored and • Differences between
architecture of the testing reported on test and production are
application clearly known
• Able to understand • A defined triage process
• Understanding of the technical gaps to meet for troubleshooting • Release and
business area requirements not configuration
• A process to manage
supported by the supported by the tool management in place
the inevitable
applications unplanned tests and and procedures
enforced
test archive exists
Performance team value
19
2012 Collaborative Consulting
20. Performance team reference model
Primary test, design, and execution team Performance engineering support skills
Planning and
Application
project
Performance architect
management
engineer
Technology
SME
Test
Results
automation
analyst Data
technician
engineering
Must determine the core team members vs. on-demand team
20
2012 Collaborative Consulting
21. Enterprise performance team
PT problem Strategy and
PT technology
resolution planning
PMO
board (architecture)**
Infrastructure**
Performance
Performance test engineering and
execution team optimization
Application
Vendor Application
support
management deployment
Vendor IBM Oracle EMC Informatica Vendor Vendor
Vendors
21
2012 Collaborative Consulting
22. Model test case execution
In the end, the test has to be run.
Prepare test
Prepare test Confirm
Select test harness online Initiate test
0 case or batch
monitoring
components
environment
readiness
case 1
messages
No
Problem
analysis and Evaluate
triage team impact of
Select test Normal test
1 case completion?
change
Yes
Yes Gather test
Analysis for Create test
results
specific report; publish
Txn RT, CPU,
DB
change? to repository 2
No
Are Categorize Can you
Implement
changes change – enter retest with Rerun the test
2 required for
Yes
change to CM
configuration
change
the
Yes
case
retest? tracking tool change?
No No
Move to next Move to next
test case 0 test scenario
22
2012 Collaborative Consulting
23. PE: Capacity planning
SA PVT CP APM PDR
Software development Performance testing and Capacity planning Application performance Problem detection and
lifecycle and architecture validation management resolution
23
2012 Collaborative Consulting
24. PE: CP (capacity planning)
The right system at the right price!
Plan for • Forecast workloads
future • Plan for usage
Analyze
• Track utilization of
existing systems current
capacity
• Track workload
Determine • Define system to
capacity support workloads
requirements • Test
• Define service
levels
Workloads drive system transactions, which drive resource utilization
24
2012 Collaborative Consulting
25. Capacity: Use of resources
The overall system has a capacity; each component has a capacity.
SERVER
WEB APP SVR
PROXY
MQ/ESB
LDAP CORBA
DCOM
Web
Services
Datacenter
25
2012 Collaborative Consulting
26. Workload model validation
Actual workload Synthetic workload
Model calibration
System System
Measured response times, Measured response times,
throughputs, utilizations, etc. throughputs, utilizations, etc.
Acceptable No
Yes
26
2012 Collaborative Consulting
27. PE: Application performance management
SA PVT CP APM PDR
Software development Performance testing and Capacity planning Application performance Problem detection and
lifecycle and architecture validation management resolution
27
2012 Collaborative Consulting
28. Five elements of APM (Gartner)
Monitoring the performance of complex distributed applications
End user experience measurement – browser/mobile
1 device
2 Create a model of the run-time environment (discovery)
Profile the performance and behavior of user-defined
3 transactions
Performance metrics from each of the
4 applications/systems technical components (Webserver,
App server, Database, etc.)
5 Application performance management database
28
2012 Collaborative Consulting
30. Track key user experience metrics
Mobile Total end-user response time
Browser rendering time
Network latency
Mobile Real User Monitoring
Rendering
30
2012 Collaborative Consulting
31. And see every hop of the transaction
Mobile
Proxy
server
Web server
App server
Data warehouse gateway
Mainframe
Database
Dynamic Transaction
Path Detection
Rendering
31
2012 Collaborative Consulting
32. PE: Problem detection and resolution
SA PVT CP APM PDR
Software development Performance testing and Capacity planning Application performance Problem detection and
lifecycle and architecture validation management resolution
32
2012 Collaborative Consulting
33. Performance issues and root-cause analysis
This leverages several knowledge areas
A solution must be found quickly (under pressure)
Performance issues are found in:
• Preproduction environment
• Production and operations environments
Key business transactions are not meeting their service level objectives:
• End user experience is degrading (acute or chronic)
• Overnight processing is taking longer
• Stability and performance issues
33
2012 Collaborative Consulting
34. When problems occur
Flash web site events (all at once)
New code released causes problems
Infrastructure upgrade
Consolidation of applications and servers
New workload model (batch and online)
34
2012 Collaborative Consulting
35. Underlying competencies
Analytical
Project Communication
thinking
management skills
problem solver
Business Monitoring and
Statistics
Knowledge tuning
Workload
Behavioral Application and
model
characteristics tool knowledge
Underlying development
competencies
Test data Test execution
Forecasting
management process
35
2012 Collaborative Consulting
36. Technical competencies
Code Deep dive Resource
Database profiling tools
utilization
monitoring tools (HP Diagnostics,
tools
CA Wily, etc, system
(Static analysis, Jprobe, etc)
diagnostics) level
End to end Comprehensive
Statistics and
performance results collection
Distributions
tools and reporting
Technical
competencies Test design Queuing
and and Test data
Little’s law
execution modeling creation
tools tools
36
2012 Collaborative Consulting
37. PE Techniques
Brainstorming Data modeling
Creating a workload model Performance testing
Triage approach Static code analysis
Logging and
System metrics collection
instrumentation
37
2012 Collaborative Consulting
38. PE roles: The team – many possible roles
Managing and developing the core team members
1 Technical Project manager
2 Performance Architect
3 Sr. Performance Engineer
4 Performance Engineer
5 Sr. Test automation technician
6 Test automation technician
7 Performance data engineer
8 Sr. Capacity planner
9 Capacity planner
10 Modeler
38
2012 Collaborative Consulting
39. Career path: Performance engineer foundation
Performance
Engineer
Grow your Performance
testing
leadership and Lead
communication technical Workload
role models
Technical Production
architecture triage
Core Additional
technical tech
competency Communication
competency
Grow your breadth of capabilities
39
2012 Collaborative Consulting
40. Case study: Preparing for a flash marketing event
Planning a large event to introduce a new product
• Send out email to all registered customers (500,000 currently), there is a link in the email.
• Run multiple TV ad’s encouraging people to register and then come to the event, results in
100,000 new registrations
• No new functionality required to support the event
• Potential 600,000 users of the web site
The business is forecasting at least a 10X increase during the
event, in terms of product sales
• How does this translate into system workload and utilization?
• Do we need more servers?
• The current system was not really designed for such a flash event
40
2012 Collaborative Consulting
41. PE: Process to prepare for the event (10X)
CP CP PVT SA
Forecast the
workload Tune application
based on results
APM PDR
Measure the current Plan and execute
workload and PT for forecast
resource utilization workload
41
2012 Collaborative Consulting
42. CP: Workload model
CP
The CP team uses this information to forecast the
new workload 10X.
Step Transaction – by product Percentage
1 Login 100
2 Search product 100
3 View product detail 100
4 Add to shopping cart 50
5 Confirm purchase method 50
6 Shipping information 50
7 Send confirmation email 50
42
2012 Collaborative Consulting
43. CP: Analyze current capacity
CP Review current Production workload, and the under lying system
utilization.
• Average workload
• Current peak workload
Response
time
Service level
100%
System utilization
43
2012 Collaborative Consulting
44. PVT: planning, executing, and analysis
PVT
• Use the workload model from CP
• Enable APM during testing
• Work with the Application Architect
Methodology is iterative and tactical
Define business
Review infrastructure
activity profiles & Design & build tests
& architecture
service levels
• Identify risk areas • Types & numbers of • Test data generation
• Review configuration users • Create test scripts
settings, topology, & sizing • Business activities & • User & transaction profiles
• Define points of frequencies • Infrastructure configuration
measurement
Iterate testing & tuning
44
2012 Collaborative Consulting
45. Questions?
Thank you!
Get your free copy
SharePath RUM today!
More information:
www.collaborative.com
info@correlsense.com
www.correlsense.com/demo
www.real-user-monitoring.com
45
2012 Collaborative Consulting
Editor's Notes
Performance is often at odds with other key quality attributes, such as flexibility, portablility, maintainability, etc.
The performance team fits inside a large context model. How does it interact with other groups?
The performance database is required to support performance analysis and analytics. This is a resource for the CP team.
You have the ability to watch/monitor every transaction for every user. What Is A Transaction?Request issued by an end-userGoes through multiple componentsEach component may be activated multiple timesNote that:Different transaction types take different paths and flowsSometimes instances of the same transaction type execute across different flows
What Is A Transaction?Request issued by an end-userGoes through multiple componentsEach component may be activated multiple timesNote that:Different transaction types take different paths and flowsSometimes instances of the same transaction type execute across different flows
The process for PDR is need for production and preproduction environments. This is required in Performance testing, critical for a key POC that demonstrates business advantage. Most POC’s experience problems along the way. Having a well defined detection and resolution process is key to success. Problems will happen and you must be ready for them, and move past them quickly.They can occur gradually or suddenly. A small change can cause big problems or disruptions. How do they manifest themselves to the end-user, or business workflow?
Flash events can wreak havoc on a system that was not designed for scaling. Database contention can come into play at much higher transaction levels. Slow memory leaks can suddenly become exposed at 10x level.Consolidation of servers or applications is a difficult tasks. Combining workloads onto one physical server that is hosting many Virtual Servers always has few unintended consequences.
How do we support the delivery of the five knowledge areas?Analytic skills are required; Decision making, Creative thinking, Learning, Problem solving, Systems thinkingBusiness knowledge – awareness of your organization and how it makes decisions (especially on budgeting)Interaction skills - Negotiation and facilitation, Leadership, Consultative/Influencing, Teamwork. Test data management – a very critical part of the Body of Knowledge.
You should correlate the TV ad to the system utilization. Did the ad drive traffic to your web site?
Each step is multiple system transactions. For instance, I have seen some login processes display too much information. In a low volume site, that might be ok. But under stress, the information for the login screen could crush the system.
Understand when the current system violates the service level. How many transactions and how far away from the Flash event goal are we? This relies on the APM tools and procedures in place. Collecting the system CPU metrics and database usage information.
Test planning, results review.Stress testing approach for the application. Most application break well before the 10X level. During the testing process, the development team will be making coding changes to help scale the application.Results reporting, detailed metrics on utilization are critical, also, often times deep diagnostics are required to find the problems.