A Modern Approach to Performance Monitoring by Cliff Crocker, VP of Product Management, SOASTA "How fast are you? How fast should you be? How do you get there? In this talk Cliff will discuss traditional approaches to performance measurement and introduce a ""RUM First"" methodology. This approach begins with capturing performance directly from the end user as the single source of truth for cross-functional organizations focused on performance. Along the way, you will discover the relationship between RUM and synthetic monitoring, learn what to measure and how to capture it and finally how perceived performance impacts human behavior and your bottom line. Akamai Edge is the premier event for Internet innovators, tech professionals and online business pioneers who together are forging a Faster Forward World. At Edge, the architects, experts and implementers of the most innovative global online businesses gather face-to-face for an invaluable three days of sharing, learning and together pushing the limits of the Faster Forward World. Learn more at: http://www.akamai.com/edge
Webpagetest.org is the de-facto benchmark to measure website performance. However, the many testing options it offers can significantly impact its results, and it has become challenging to decide which ones to use. Based on real-life measurements of popular websites, this presentation explores its repeatability and relevance to help its users define Webpagetest settings that best meet their needs.
Cliff Crocker discusses best practices for measuring what matters and applying an understandable methodology that achieves what we are all after: happier users.
The document discusses how Akamai's Intelligent Internet Platform addresses challenges posed by increasingly sophisticated websites and rising consumer expectations for faster load times and richer content. It does this through a global network of servers that optimize routing, cache content closer to users, compress data and prefetch resources to accelerate page loads. Case studies show how Akamai has helped customers like Best Buy and Urban Outfitters improve performance, scale to handle traffic spikes and reduce infrastructure costs.
A lap around 4 advanced techniques or services to complement an Azure Web App solution. Application Gateway with Web Application Firewall Azure SQL VNet Integration with (ASE v2) Azure CDN Auto Scale & Visual Studio Load Testing
This document discusses scaling digital asset management systems to handle large repositories. It begins by describing challenges that can arise from trying to scale a DAM system without optimization. It then provides recommendations for optimizing asset processing workflows and configurations. Finally, it outlines several architectural approaches for scaling a DAM system, such as using separate instances for ingestion/processing and executing intensive tasks. The goal is to first optimize and then scale the system in a way that matches asset usage and adds necessary resources.
The document discusses optimizing web performance for mobile devices. It covers mobile web platforms and browsers, the importance of performance on mobile, tools for measuring performance, optimizing initial loading and above-the-fold content within 1 second, and maintaining responsiveness. The key recommendations are to measure on real devices, avoid redirects, reduce requests, load above-the-fold content quickly and defer the rest, and prioritize simplicity over complex designs and frameworks.
A tutorial on how to improve performance of webpages. Covers most of the artifacts needed for a good audit score on browsers.
The document discusses Adobe Experience Manager's capabilities for responsive web design. It provides an overview of responsive vs adaptive design and how AEM allows editing responsive layouts through a grid system. It then details how to set up responsive editing in AEM, including enabling the responsive emulator, layouting mode, and responsive grid. It also covers developing components for the responsive grid and leveraging breakpoints.
The document discusses Akamai's content delivery network and traffic engineering with Akamai. It provides an overview of Akamai's global intelligent platform and typical daily traffic volumes. It also covers how Akamai mapping works and why peering with Akamai benefits both Akamai and internet service providers. The document analyzes two scenarios involving traffic tuning during a cable break and issues with incomplete route announcements. It concludes with recommendations for internet service providers to maintain complete route announcements and work with Akamai on traffic engineering solutions.
Dell uses Akamai's Enterprise Application Access (EAA) to securely test changes to Dell.com redirects and caching rules. EAA allows Dell developers and testers to access non-production environments from various devices internally and externally without a VPN. This helps Dell validate complex configurations before deploying updates to production and identify issues by seeing which redirect rule was triggered. Dell installed EAA appliances in their environment which use reverse proxies and Active Directory integration to securely grant internal users access for automated testing of Akamai rules.
This document provides an overview of techniques for developing high performance web applications. It discusses why front-end performance matters, and outlines best practices for optimizing page load times, using responsive interfaces, loading and executing JavaScript efficiently, and accessing data. The presentation recommends tools for monitoring and improving performance, such as Firebug, Page Speed, and YSlow.
Do you have a lot of complex jobs that you need to run as part of your application? Do they consist of multiple tasks and you wonder how to orchestrate them properly? Do you want to be able to easily scale their execution? Is availability of your workers important to you? If you answer “Yes” to these questions then AWS Simple Workflow is the right tool for you. In this talk we will go through Amazon SWF and Java Flow Framework and you will see how to get a distributed job execution engine right out of the box. We will also compare SWF to alternative solutions, discuss real life experience, and of course enjoy a live demo. The talk will be most useful to everyone who is interested in the design of distributed systems and is new to AWS SWF.
Integration is not hip but relevant, especially with respect to the ongoing digital transformation. What does this mean in concrete terms with modern software architectures? Traditionally, monolithic ESB platforms are used in the integration space. Is this still in keeping with the times? We think not. Why? Today’s requirements are volatile, and data loads are increasing constantly. So modern integration architectures need to be scalable, flexible, and easy to adjust. This session discusses requirements for integration architectures based on reactive principles and patterns. It also looks at possible solution architectures based on groundbreaking technologies such as Akka and modern platform solutions (on premises and cloud).
The Amazon Simple Workflow (Amazon SWF) service is a building block for highly scalable applications. Where Amazon EC2 helps developers scale compute and Amazon S3 helps developers scale storage, Amazon SWF helps developers scale their business logic. Customers use Amazon SWF to coordinate, operate, and audit work across multiple machines—across the cloud or their own data centers. In this power-packed session, we demonstrate the power of workflows through 7 customer stories and 7 use cases, in 7 minutes each. We show how you can use Amazon SWF for curating social media streams, processing user-generated video, managing CRM workflows, and more. We show how customers are using Amazon SWF to automate virtually any script, library, job, or workflow and scale their application pipeline cost-effectively.
Akamai Edge 14 - Discussion on RUM, Synthetic and setting realistic and meaningful performance goals.
This document discusses various metrics for measuring website performance and user experience. It outlines different types of metrics including: - Network metrics like DNS resolution, TCP connection times, and time to first byte. - Browser metrics like start render time, DOM loading/ready times, and page load times. - Resource-level metrics obtained from the Resource Timing API like individual asset load times and response sizes. - User-centric metrics like Speed Index, time to visible content, and metrics for single-page applications without traditional page loads. It emphasizes the importance of measuring real user monitoring data alongside synthetic tests, and looking at higher percentiles rather than just averages due to variability in user environments and network conditions
This document discusses various metrics for measuring website performance. It begins by noting that there are many metrics to consider and no single metric tells the whole story. It then discusses several key metrics for measuring different aspects of performance, including: - Front-end metrics like start render, DOM loading/ready, and page load that can isolate front-end from back-end performance. - Network metrics like DNS and TCP timings that provide insight into connectivity issues. - Resource timing metrics that measure individual assets to understand impacts of third parties and CDNs. - User timing metrics like measuring above-the-fold content that capture user experience. It emphasizes the importance of considering real user monitoring data alongside
There’s no one-size-fits-all approach to metrics. In this session, Cliff Crocker and I walk through various metrics that answer performance questions from multiple perspectives — from designer and DevOps to CRO and CEO. You’ll walk away with a better understanding of your options, as well as a clear understanding of how to choose the right metric for the right audience.
Integrating content delivery networks into your application infrastructure can offer many benefits, including major performance improvements for your applications. So understanding how CDNs perform — especially for your specific use cases — is vital. However, testing for measurement is complicated and nuanced, and results in metric overload and confusion. It's becoming increasingly important to understand measurement techniques, what they're telling you, and how to apply them to your actual content. In this session, we'll examine the challenges around measuring CDN performance and focus on the different methods for measurement. We'll discuss what to measure, important metrics to focus on, and different ways that numbers may mislead you. More specifically, we'll cover: Different techniques for measuring CDN performance Differentiating between network footprint and object delivery performance Choosing the right content to test Core metrics to focus on and how each impacts real traffic Understanding cache hit ratio, why it can be misleading, and how to measure for it
As Walmart.com’s former head of Performance and Reliability, Cliff Crocker knows large scale web performance. Now SOASTA’s VP of products, Cliff is pouring his passion and expertise into cloud testing to solve the biggest challenges in mobile and web performance. The holiday rush of mobile and web traffic to your web site has the potential for unprecedented success or spectacular public failure. The world’s leading retailers have turned to the cloud to assure that no matter what load, mobile and web apps will delight customers and protect revenue. Join us as Cliff explores the key criteria for holiday web performance readiness: Closing the gap in front- and back-end web performance and reliability Collecting real user data to define the most realistic test scenarios Preparing properly for the virtual walls of traffic during peak events Leveraging CloudTest technology, as have 6 of 10 leading retailers
You want a single, unicorn metric that magically sums up the user experience, business value, and numbers that DevOps cares about, but so far, you're just not getting it. So where do you start? In this talk at the 2015 Velocity conference in Santa Clara, Cliff Crocker and I walked through various metrics that answer performance questions from multiple perspectives -- from designer and DevOps to CRO and CEO.
Not surprisingly, there’s no one-size-fits-all performance metric (though life would be simpler if there were). Different metrics will give you different critical insights into whether or not your pages are delivering the results you want — both from your end user’s perspective and ultimately from your organization’s perspective. Join Tammy Everts, and walk through various metrics that answer performance questions from multiple perspectives. You’ll walk away with a better understanding of your options, as well as a clear understanding of how to choose the right metric for the right audience.
Not surprisingly, there’s no one-size-fits-all performance metric (though life would be simpler if there were). Different metrics will give you different critical insights into whether or not your pages are delivering the results you want — both from your end user’s perspective and ultimately from your organization’s perspective. Join Tammy Everts, and walk through various metrics that answer performance questions from multiple perspectives. You’ll walk away with a better understanding of your options, as well as a clear understanding of how to choose the right metric for the right audience.
RUM and synthetic monitoring each provide valuable but different performance data. RUM captures real user behavior but numbers vary greatly depending on user environments, while synthetic provides consistent baseline data but doesn't reflect real users. Both data sets are needed to understand a site's true performance across different user scenarios. There is no single performance number, and the right metrics depend on the intended audience and business goals.
The document discusses client side performance testing. It defines client side performance as how fast a page loads for a single user on a browser or mobile device. Good client side performance is important for user experience and business metrics like sales. It recommends rules for faster loading websites, and introduces the WebPageTest tool for measuring client side performance metrics from multiple locations. WebPageTest provides waterfall views, filmstrip views, packet captures and reports to analyze page load times and identify optimization opportunities.
This presentation is the first in a series on Improving Rails application performance. This session covers the basic motivations and goals for improving performance, the best way to approach a performance assessment, and a review of the tools and techniques that will yield the best results. Tools covered include: Firebug, yslow, page speed, speed tracer, dom monster, request log analyzer, oink, rack bug, new relic rpm, rails metrics, showslow.org, msfast, webpagetest.org and gtmetrix.org. The upcoming sessions will focus on: Improving sql queries, and active record use Improving general rails/ruby code Improving the front-end And a final presentation will cover how to be a more efficient and effective developer! This series will be compressed into a best of session for the 2010 http://windycityRails.org conference
My presentation at the Zycko breakfast session... About why your users don't like to wait and why you should care as a site owner. This presentation covers the importance of perception of speed, navigation and how to do proper performance monitoring...
This document discusses modern browser APIs that can improve web application performance. It covers Navigation Timing, Resource Timing, and User Timing which provide standardized ways to measure page load times, resource load times, and custom events. Other APIs discussed include the Performance Timeline, Page Visibility, requestAnimationFrame for script animations, High Resolution Time for more precise timestamps, and setImmediate for more efficient script yielding than setTimeout. These browser APIs give developers tools to assess and optimize the performance of their applications.
The document provides an overview of Daniel Austin's Web Performance Boot Camp. The class aims to (1) provide an understanding of web performance, (2) empower attendees to identify and resolve performance issues, and (3) demonstrate common performance tools. The class covers topics such as the impact of performance on business, definitions of performance, statistical analysis, queuing theory, the OSI model, and the MPPC model for analyzing the multiple components that determine overall web performance. Attendees will learn tools like Excel, web testing tools, browser debugging tools, and optional tools like R and Mathematica.
This document discusses the importance of performance testing and provides an introduction to the topic. It notes that performance testing determines how a system behaves under different loads and helps identify bottlenecks. The document outlines why performance testing is important from a user experience perspective, discussing metrics like page load times and the financial costs of poor performance. It then covers various performance testing approaches, targets, levels, and common metrics used to evaluate performance.
My slides from DrupalJam 2014... About why users abandon your website and best practices to align content and speed to create a fast user experience, and continue to keep it aligned for every release
The document discusses effective strategies for monitoring client-side web performance. It recommends collecting both real user monitoring metrics from actual users as well as synthetic metrics from automated tests. It describes tools like Navigation Timing API, paint metrics, custom metrics, and open-source libraries that can capture metrics. It also discusses storing and visualizing metrics with tools like Graphite and Grafana and how to reduce noise and account for environment differences when analyzing performance data. The overall goal is to utilize performance metrics to inform decisions that improve the user experience.
Why performance testing is important? Introduction to performance testing. Load profiles, metrics Performance testing tools Implementation process Performance testing engineer skills JMeter intro LINKS: About performance testing: http://docplayer.net/29696161-Performance-matters-key-consumer-insights.html http://www.softwaretestingclass.com/what-is-performance-testing/ https://www.blazemeter.com/blog http://revolutionit.com.au/performance-testing-digital-projects-dont-leave-it-to-the-developers/ https://www.youtube.com/embed/61Kkgnx-zF8?list=PLSjEh0z5QH9lKpMO4Nf3buFiP7tt0gTRN Concurrent users calculation: https://blog.xceptance.com/2013/07/26/concurrent-users-the-art-of-calculation/ https://techbeacon.com/how-many-virtual-users-do-i-need-load-testing https://www.webperformance.com/library/tutorials/CalculateNumberOfLoadtestUsers/ Browser performance: https://www.slideshare.net/nicjansma/measuring-real-user-performance-in-the-browser Books for start: “Web Load Testing For Dummies”, Scott Barber with Colin Mason “JMeter Cookbook”, Bayo Erinle
ThousandEyes provides network intelligence and monitoring of web performance. It offers different test types - HTTP server tests measure server response times, page load tests measure loading of full web pages in a browser, and web transaction tests measure performance of specific user interactions on a site. The tests provide metrics on response times, throughput, errors and performance of individual page components from different network locations and internet providers. The document recommends tips for optimizing web transactions such as adjusting timeouts, configuring start/stop steps, using XPath locators, and inserting wait conditions. It demonstrates creating and running page load, HTTP server and web transaction tests to monitor web performance.
This document discusses edge security and Akamai's intelligent edge security platform. It notes that security remains a challenge as the threat landscape and attack surfaces continue to change rapidly. Akamai's edge security platform provides strategic protection around applications, infrastructure, and users by enforcing consistent security policies across its global network. It offers visibility into billions of daily attacks and adapts to protect assets anywhere. The platform includes services like DDoS protection, web application firewall, zero trust network access, and bot management.
The document discusses replacing recovery with resilience in cloud infrastructure. It summarizes Akamai's experience in maintaining operations during various disruptive events like cable disruptions, natural disasters, and large DDoS attacks. It promotes Akamai's cloud security and delivery platform that provides solutions like DDoS protection, bot management, web application protection, and acceleration to ensure superior digital experience and security. It emphasizes choosing a strategic partner with experience in multiplying capabilities and acting as a shield.