The document discusses Websockets and compares them to HTTP. It provides an overview of Websockets including how they work, specifications, and examples of using Websockets in JavaScript, Android Java, and Java server-side code with the jquery-websocket library. Benefits highlighted include full-duplex communication, lower overhead than HTTP, and lower latency.
The Supply Chain Business Consultants is a consulting firm established in 1992 that is headquartered in Belgium with offices throughout Europe and India. They have over 60 highly experienced consultants and generated over 10 million euros in revenue in 2008. They offer strategic supply chain consulting services in three main areas: supply chain strategy and performance, supply chain process excellence, and supply chain performance turnaround.
This document discusses techniques for improving global web performance and content delivery networks (CDNs). It begins by explaining how internet speeds vary globally and within Korea. It then discusses how CDNs work by caching content at the edge to reduce latency. Both national and global CDNs are described, with global CDNs having points of presence around the world. Metrics for measuring website performance like waterfall charts are also presented. Methods for optimizing websites through techniques like initializing TCP connections and front-end optimizations are then covered. The document concludes by discussing some advanced topics like mobile network latency.
This document discusses measuring and analyzing web latency. It provides an overview of key latency metrics like server rendering time and time to load. It describes how to monitor latency over time and analyze trends. It also discusses testing latency through synthetic benchmarks and real user monitoring. The document emphasizes the importance of understanding client-side rendering times and how latency can be impacted by many factors.
The document discusses Seam, an open source Java web framework. It outlines Seam's key features like conversation scope for managing state across HTTP requests and atomic conversations. Seam provides tools for building applications quickly including seam-gen for project generation and validation integration. The document also mentions developer tools like JBoss Developer Studio and possibilities for using Flex as an alternative view layer.
Speed is Essential for a Great Web ExperienceDigicure ApS
Andy Davies' slides fra Digicures web performance seminar på Bella Sky, 24. oktober 2012.
Den engelske ekspert og freelance konsulent, Andy Davies, har været bidt af emnet om god web performance siden 90'erne. Andy hjælper virksomheder med at måle, analysere og forbedre performance og stabiliteten af deres websites.
Selvom hastighed er vigtig for en god online oplevelse, bliver det ofte overset. Andy Davies vil fortælle hvordan hastighed påvirker brugeroplevelsen på et website og afdække hvordan hastighed kan måles og analyseres.
The document discusses Websockets and compares them to HTTP. It provides an overview of Websockets including how they work, specifications, and examples of using Websockets in JavaScript, Android Java, and Java server-side code with the jquery-websocket library. Benefits highlighted include full-duplex communication, lower overhead than HTTP, and lower latency.
The Supply Chain Business Consultants is a consulting firm established in 1992 that is headquartered in Belgium with offices throughout Europe and India. They have over 60 highly experienced consultants and generated over 10 million euros in revenue in 2008. They offer strategic supply chain consulting services in three main areas: supply chain strategy and performance, supply chain process excellence, and supply chain performance turnaround.
This document discusses techniques for improving global web performance and content delivery networks (CDNs). It begins by explaining how internet speeds vary globally and within Korea. It then discusses how CDNs work by caching content at the edge to reduce latency. Both national and global CDNs are described, with global CDNs having points of presence around the world. Metrics for measuring website performance like waterfall charts are also presented. Methods for optimizing websites through techniques like initializing TCP connections and front-end optimizations are then covered. The document concludes by discussing some advanced topics like mobile network latency.
This document discusses measuring and analyzing web latency. It provides an overview of key latency metrics like server rendering time and time to load. It describes how to monitor latency over time and analyze trends. It also discusses testing latency through synthetic benchmarks and real user monitoring. The document emphasizes the importance of understanding client-side rendering times and how latency can be impacted by many factors.
The document discusses Seam, an open source Java web framework. It outlines Seam's key features like conversation scope for managing state across HTTP requests and atomic conversations. Seam provides tools for building applications quickly including seam-gen for project generation and validation integration. The document also mentions developer tools like JBoss Developer Studio and possibilities for using Flex as an alternative view layer.
Speed is Essential for a Great Web ExperienceDigicure ApS
Andy Davies' slides fra Digicures web performance seminar på Bella Sky, 24. oktober 2012.
Den engelske ekspert og freelance konsulent, Andy Davies, har været bidt af emnet om god web performance siden 90'erne. Andy hjælper virksomheder med at måle, analysere og forbedre performance og stabiliteten af deres websites.
Selvom hastighed er vigtig for en god online oplevelse, bliver det ofte overset. Andy Davies vil fortælle hvordan hastighed påvirker brugeroplevelsen på et website og afdække hvordan hastighed kan måles og analyseres.
Speed is Essential for a Great Web Experience (Canvas Conf Version)Andy Davies
Speed is essential for a good user experience on the web. Research has shown that page load times over 1 second can negatively impact user behavior like concentration and abandonment rates. Factors that affect page load times include front-end code, images, third-party scripts, redirects, and HTTP requests. Key ways to improve performance include optimizing front-end code, compressing images, loading scripts asynchronously, minimizing redirects, caching resources, and measuring real user performance. The goal is to provide users with fast response times across all devices.
The Tellurium Automated Testing Framework (Tellurium) is a UI module-based web automated testing framework.
The Tellurium framework is written in Groovy and Java. The test cases can be written in Java, Groovy, or pure DSL. You do not need to know Groovy before you use it. Detailed Introduction, Frequent Asked Questions, and illustrative examples are provided. We expect and welcome your contributions.
The document discusses alternatives to using the onload event to measure website performance. It notes limitations of onload for single-page applications and that it often misses perceived performance. Several alternative events and methods are proposed, including DOMContentLoaded, custom events, User Timing API, and tracking key user behaviors. Ultimately, it suggests the best approach depends on user needs and that the goal should be a consistent methodology for determining when a site is usable.
Tellurium is a UI module based web testing framework. The UI module is a collection of UI elements you group together. Usually, the UI module represents a composite UI object in the format of nested basic UI elements. The UI module makes it possible to build UI elements' locators at run time. The framework does object to locator mapping (OLM) automatically at run time so that you can define UI objects simply by their attributes and write your selenium tests just like writing JUnit/TestNG tests. Since the framework constructs the actual locator automatically at run-time and it uses the Group Locating Concept (GLC) to exploit information inside a collection of UI components to help finding their locators, Tellurium is more robust, flexible, reusable compared with the Selenium testing framework.
This is a short version.
Fronteers Spring Conference Amsterdam 2016 keynote Kristian Sköld
Change initiatives usually don't fail because the change was introduced too early, but rather because it was introduced too late after problems had already manifested. Godin notes that change almost always fails due not to being premature but to occurring too late after issues have already surfaced and become harder to address. The key is recognizing the need for change before problems become deeply entrenched.
Comet: an Overview and a New Solution Called JabbifyBrian Moschel
Brian Moschel delivered this talk at the JS.Chi() April 2009 meetup. This talk provides an overview of Comet, also known as HTTP Push, covering how it works on the server and client, several implementation options, and using a new Comet API called Jabbify in an interactive demo.
Comet, Simplified, with Jabbify Comet ServiceBrian Moschel
The document discusses Comet and how Jabbify provides a simplified approach to implementing Comet through a JavaScript API and GET requests without requiring custom server setup, allowing for real-time updates between clients through a simple and scalable solution. Jabbify is presented as easier to use than traditional Comet implementations through its rapid setup and scaling capabilities without resource-intensive server requirements.
How Terracotta enables scaled Spring/Hibernate applications. Presented at Chicago JUG in March 2009 by Alex Miller (http://tech.puredanger.com / @puredanger)
High availability is ultimately measured by the end user experience and minimizing downtime. The goal is to balance business needs with technical capabilities and costs. A system is considered highly available if it meets the agreed upon availability percentage. SharePoint 2013 requires all servers in a farm to be located in the same data center, so redundancy between data centers is not supported. Load balancing multiple web frontends across servers improves availability.
- The document discusses the CloudKit framework, which allows building RESTful web applications and services using Rack, HTTP, and JSON.
- CloudKit exposes collections of JSON documents through a RESTful interface and handles common tasks like content negotiation, versioning, and concurrency control using HTTP features like ETags.
- Examples are given of creating, retrieving, updating and deleting resources representing todo items using CloudKit and making HTTP requests with curl. This allows building a basic RESTful todo application within a few lines of code.
Performance, Games, and Distributed Testing in JavaScriptjeresig
This document discusses various techniques for measuring and optimizing JavaScript performance, including profiling tools in browsers like Firebug and Safari. It also addresses challenges in building multiplayer JavaScript games, such as latency issues, and proposes solutions like combining elements of strategy, intelligence and accuracy. The document concludes by covering distributed and automated testing techniques like TestSwarm that can help address challenges of testing JavaScript across many browsers and platforms.
Metrics, metrics everywhere (but where the heck do you start?) SOASTA
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
Velocity NYC: Metrics, metrics everywhere (but where the heck do you start?)Cliff Crocker
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
Metrics, metrics everywhere (but where the heck do you start?)Tammy Everts
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.
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
Rail Performance in the Cloud - OpeningEngine Yard
This document discusses optimizing performance for Ruby on Rails applications in the cloud. It begins with introductions and an agenda for the event. It then discusses why Rails development is faster and how its conventions allow developers to focus on the application. It explains how cloud infrastructure provides instant, programmable resources on demand and only charges for what is used. It outlines how performance impacts user satisfaction, engagement, organic search rankings and competitive advantage. It then gets more concrete by discussing performance thresholds and load times for 100 Rails sites. Finally, it discusses the top five sources of high performance and how to optimize page construction, application code, software architecture, component selection and infrastructure capacity.
Speed is Essential for a Great Web Experience (Canvas Conf Version)Andy Davies
Speed is essential for a good user experience on the web. Research has shown that page load times over 1 second can negatively impact user behavior like concentration and abandonment rates. Factors that affect page load times include front-end code, images, third-party scripts, redirects, and HTTP requests. Key ways to improve performance include optimizing front-end code, compressing images, loading scripts asynchronously, minimizing redirects, caching resources, and measuring real user performance. The goal is to provide users with fast response times across all devices.
The Tellurium Automated Testing Framework (Tellurium) is a UI module-based web automated testing framework.
The Tellurium framework is written in Groovy and Java. The test cases can be written in Java, Groovy, or pure DSL. You do not need to know Groovy before you use it. Detailed Introduction, Frequent Asked Questions, and illustrative examples are provided. We expect and welcome your contributions.
The document discusses alternatives to using the onload event to measure website performance. It notes limitations of onload for single-page applications and that it often misses perceived performance. Several alternative events and methods are proposed, including DOMContentLoaded, custom events, User Timing API, and tracking key user behaviors. Ultimately, it suggests the best approach depends on user needs and that the goal should be a consistent methodology for determining when a site is usable.
Tellurium is a UI module based web testing framework. The UI module is a collection of UI elements you group together. Usually, the UI module represents a composite UI object in the format of nested basic UI elements. The UI module makes it possible to build UI elements' locators at run time. The framework does object to locator mapping (OLM) automatically at run time so that you can define UI objects simply by their attributes and write your selenium tests just like writing JUnit/TestNG tests. Since the framework constructs the actual locator automatically at run-time and it uses the Group Locating Concept (GLC) to exploit information inside a collection of UI components to help finding their locators, Tellurium is more robust, flexible, reusable compared with the Selenium testing framework.
This is a short version.
Fronteers Spring Conference Amsterdam 2016 keynote Kristian Sköld
Change initiatives usually don't fail because the change was introduced too early, but rather because it was introduced too late after problems had already manifested. Godin notes that change almost always fails due not to being premature but to occurring too late after issues have already surfaced and become harder to address. The key is recognizing the need for change before problems become deeply entrenched.
Comet: an Overview and a New Solution Called JabbifyBrian Moschel
Brian Moschel delivered this talk at the JS.Chi() April 2009 meetup. This talk provides an overview of Comet, also known as HTTP Push, covering how it works on the server and client, several implementation options, and using a new Comet API called Jabbify in an interactive demo.
Comet, Simplified, with Jabbify Comet ServiceBrian Moschel
The document discusses Comet and how Jabbify provides a simplified approach to implementing Comet through a JavaScript API and GET requests without requiring custom server setup, allowing for real-time updates between clients through a simple and scalable solution. Jabbify is presented as easier to use than traditional Comet implementations through its rapid setup and scaling capabilities without resource-intensive server requirements.
How Terracotta enables scaled Spring/Hibernate applications. Presented at Chicago JUG in March 2009 by Alex Miller (http://tech.puredanger.com / @puredanger)
High availability is ultimately measured by the end user experience and minimizing downtime. The goal is to balance business needs with technical capabilities and costs. A system is considered highly available if it meets the agreed upon availability percentage. SharePoint 2013 requires all servers in a farm to be located in the same data center, so redundancy between data centers is not supported. Load balancing multiple web frontends across servers improves availability.
- The document discusses the CloudKit framework, which allows building RESTful web applications and services using Rack, HTTP, and JSON.
- CloudKit exposes collections of JSON documents through a RESTful interface and handles common tasks like content negotiation, versioning, and concurrency control using HTTP features like ETags.
- Examples are given of creating, retrieving, updating and deleting resources representing todo items using CloudKit and making HTTP requests with curl. This allows building a basic RESTful todo application within a few lines of code.
Performance, Games, and Distributed Testing in JavaScriptjeresig
This document discusses various techniques for measuring and optimizing JavaScript performance, including profiling tools in browsers like Firebug and Safari. It also addresses challenges in building multiplayer JavaScript games, such as latency issues, and proposes solutions like combining elements of strategy, intelligence and accuracy. The document concludes by covering distributed and automated testing techniques like TestSwarm that can help address challenges of testing JavaScript across many browsers and platforms.
Metrics, metrics everywhere (but where the heck do you start?) SOASTA
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
Velocity NYC: Metrics, metrics everywhere (but where the heck do you start?)Cliff Crocker
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
Metrics, metrics everywhere (but where the heck do you start?)Tammy Everts
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.
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
Rail Performance in the Cloud - OpeningEngine Yard
This document discusses optimizing performance for Ruby on Rails applications in the cloud. It begins with introductions and an agenda for the event. It then discusses why Rails development is faster and how its conventions allow developers to focus on the application. It explains how cloud infrastructure provides instant, programmable resources on demand and only charges for what is used. It outlines how performance impacts user satisfaction, engagement, organic search rankings and competitive advantage. It then gets more concrete by discussing performance thresholds and load times for 100 Rails sites. Finally, it discusses the top five sources of high performance and how to optimize page construction, application code, software architecture, component selection and infrastructure capacity.
Similar to Speed is Essential for a Great Web Experience (oredev) (20)
AB Testing, Ads and other 3rd party tags - London WebPerf - March 2018Andy Davies
Talk at Smashing Conf - 7th Feb 2018 (Video - https://vimeo.com/254703766)
Explores some of the issues that 3rd-party tags introduce when we add them to our sites, some ways of measuring the impact, and challenges we still have
AB Testing, Ads and other 3rd party tags - SmashingConf London - 2018Andy Davies
Talk at Smashing Conf - 7th Feb 2018 (Video - https://vimeo.com/254703766)
Explores some of the issues that 3rd-party tags introduce when we add them to our sites, some ways of measuring the impact, and challenges we still have
Inspecting iOS App Traffic with JavaScript - JSOxford - Jan 2018Andy Davies
This document discusses inspecting iOS app traffic with JavaScript by injecting scripts using Frida. It demonstrates capturing encrypted network traffic from an iOS app, extracting the TLS master secret and client/server randoms using a Frida script, and sending these values to the host computer to allow decrypting the traffic with Wireshark. The key steps are: using Frida to inject a script into an app, hooking the TLS PRF function to extract secret values, and sending these to the host to decrypt the HTTPS traffic in Wireshark. With these techniques, patterns in encrypted app traffic can be observed.
Slides from my talk at Bristol WebPerf Meetup 2017-07-20 where I talked about some of the approaches I use to persuade people that they should invest in making their sites faster
Speed: The 'Forgotten' Conversion FactorAndy Davies
Speed is a critical factor when it comes to converting browsers into buyers but it's often forgotten and other factors prioritised instead. Using real data from UK retailers this talk explores the relationship between speed and conversion
Building an Appier Web - London Web Standards - Nov 2016Andy Davies
Explores progressive web apps, what advantages they have versus native apps, how to build, and test them, and some of the challenges we still have ahead.
Slides from talk at London Web Standards, Nov 2016
Building an Appier Web - Velocity Amsterdam 2016Andy Davies
Explores progressive web apps, what advantages they have versus native apps, how to build, and test them, and some of the challenges we still have ahead.
Slides from talk at Velocity Amsterdam 2016
The Case for HTTP/2 - GreeceJS - June 2016Andy Davies
HTTP/2 is here but why do we need it, how is it different to HTTP/1.1 and what does the mean for developers?
Slides from my talk at GreeceJS in Athens, June 2016
Slides from my talk at NCC Group's Web Performance Day in May 2016.
Compares the features of apps and the web, what's great about each and explores some of the technologies that will allow us to build websites that can deliver native like experiences.
The Fast, The Slow and The Unconverted - Emerce Conversion 2016Andy Davies
Slides from my talk at Emerce Conversion, Amsterdam on the importance of performance(page speed) for conversion.
Explore some of the performance issues we face when relying on third-party CRO products / services
The Case for HTTP/2 - Internetdagarna 2015 - StockholmAndy Davies
HTTP/2 is here but why do we need it, how is it different to HTTP/1.1 and what does the mean for developers?
Slides from my talk at Internetdagarna 2015, Stockholm
The document discusses how mobile sites are getting slower due to larger page sizes from images, CSS, JavaScript and fonts. It provides tips for optimizing images, such as using responsive images and smaller image sizes. It also recommends prioritizing critical content over non-essential elements like unnecessary JavaScript and web fonts to improve page load times.
The Case for HTTP/2 - EpicFEL Sept 2015Andy Davies
HTTP/2 is here but why do we need it, and how is it different to HTTP/1.1?
Video - https://www.youtube.com/watch?v=ob-CnA9YmiI
These are the slides from my talk at Front-End London's one day conference, EpicFEL
Speed matters, So why is your site so slow?Andy Davies
Slides from my talk at ReDevelop 2015
Covers business case for web performance, along with the fundamentals of how latency and the critical rendering path affect page load performance
HTTP/2 addresses limitations in HTTP/1.x by multiplexing requests over a single TCP connection, compressing headers, and allowing servers to push responses. It leads to more efficient use of network resources and faster page loads. While browser support is good, server implementations are still maturing and need to fully support HTTP/2 features like streams, dependencies, and server push to provide optimizations. Efficient TLS is also important to avoid delays in taking advantage of HTTP/2 performance benefits.
HTTP/2 provides improvements over HTTP/1.1 such as multiplexed requests, header compression and priority hints from browsers that can reduce latency. While it shows benefits in testing, real-world impacts may be more modest depending on server and client configurations. Further optimizations are still needed and HTTP/2 opens up new possibilities around features like server pushing and progressive content delivery that could enhance performance.
This document discusses the importance of website speed and performance. It notes that most top retail sites take over 3 seconds to load critical content, and median page load times have slowed by 23% year-over-year. Faster sites see benefits like 10% higher conversions. Network latency has a greater impact on performance than bandwidth. Techniques like preloading fonts and images can help mitigate latency. Frameworks and features like service workers may also help if designed deliberately for performance. Regular measurement and setting performance budgets are recommended to build fast user experiences.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/07/intels-approach-to-operationalizing-ai-in-the-manufacturing-sector-a-presentation-from-intel/
Tara Thimmanaik, AI Systems and Solutions Architect at Intel, presents the “Intel’s Approach to Operationalizing AI in the Manufacturing Sector,” tutorial at the May 2024 Embedded Vision Summit.
AI at the edge is powering a revolution in industrial IoT, from real-time processing and analytics that drive greater efficiency and learning to predictive maintenance. Intel is focused on developing tools and assets to help domain experts operationalize AI-based solutions in their fields of expertise.
In this talk, Thimmanaik explains how Intel’s software platforms simplify labor-intensive data upload, labeling, training, model optimization and retraining tasks. She shows how domain experts can quickly build vision models for a wide range of processes—detecting defective parts on a production line, reducing downtime on the factory floor, automating inventory management and other digitization and automation projects. And she introduces Intel-provided edge computing assets that empower faster localized insights and decisions, improving labor productivity through easy-to-use AI tools that democratize AI.
Video traffic on the Internet is constantly growing; networked multimedia applications consume a predominant share of the available Internet bandwidth. A major technical breakthrough and enabler in multimedia systems research and of industrial networked multimedia services certainly was the HTTP Adaptive Streaming (HAS) technique. This resulted in the standardization of MPEG Dynamic Adaptive Streaming over HTTP (MPEG-DASH) which, together with HTTP Live Streaming (HLS), is widely used for multimedia delivery in today’s networks. Existing challenges in multimedia systems research deal with the trade-off between (i) the ever-increasing content complexity, (ii) various requirements with respect to time (most importantly, latency), and (iii) quality of experience (QoE). Optimizing towards one aspect usually negatively impacts at least one of the other two aspects if not both. This situation sets the stage for our research work in the ATHENA Christian Doppler (CD) Laboratory (Adaptive Streaming over HTTP and Emerging Networked Multimedia Services; https://athena.itec.aau.at/), jointly funded by public sources and industry. In this talk, we will present selected novel approaches and research results of the first year of the ATHENA CD Lab’s operation. We will highlight HAS-related research on (i) multimedia content provisioning (machine learning for video encoding); (ii) multimedia content delivery (support of edge processing and virtualized network functions for video networking); (iii) multimedia content consumption and end-to-end aspects (player-triggered segment retransmissions to improve video playout quality); and (iv) novel QoE investigations (adaptive point cloud streaming). We will also put the work into the context of international multimedia systems research.
Building an Agentic RAG locally with Ollama and MilvusZilliz
With the rise of Open-Source LLMs like Llama, Mistral, Gemma, and more, it has become apparent that LLMs might also be useful even when run locally. In this talk, we will see how to deploy an Agentic Retrieval Augmented Generation (RAG) setup using Ollama, with Milvus as the vector database on your laptop. That way, you can also avoid being Rate Limited by OpenAI like I have been in the past.
Quantum Communications Q&A with Gemini LLM. These are based on Shannon's Noisy channel Theorem and offers how the classical theory applies to the quantum world.
Data Protection in a Connected World: Sovereignty and Cyber Securityanupriti
Delve into the critical intersection of data sovereignty and cyber security in this presentation. Explore unconventional cyber threat vectors and strategies to safeguard data integrity and sovereignty in an increasingly interconnected world. Gain insights into emerging threats and proactive defense measures essential for modern digital ecosystems.
GDG Cloud Southlake #34: Neatsun Ziv: Automating AppsecJames Anderson
The lecture titled "Automating AppSec" delves into the critical challenges associated with manual application security (AppSec) processes and outlines strategic approaches for incorporating automation to enhance efficiency, accuracy, and scalability. The lecture is structured to highlight the inherent difficulties in traditional AppSec practices, emphasizing the labor-intensive triage of issues, the complexity of identifying responsible owners for security flaws, and the challenges of implementing security checks within CI/CD pipelines. Furthermore, it provides actionable insights on automating these processes to not only mitigate these pains but also to enable a more proactive and scalable security posture within development cycles.
The Pains of Manual AppSec:
This section will explore the time-consuming and error-prone nature of manually triaging security issues, including the difficulty of prioritizing vulnerabilities based on their actual risk to the organization. It will also discuss the challenges in determining ownership for remediation tasks, a process often complicated by cross-functional teams and microservices architectures. Additionally, the inefficiencies of manual checks within CI/CD gates will be examined, highlighting how they can delay deployments and introduce security risks.
Automating CI/CD Gates:
Here, the focus shifts to the automation of security within the CI/CD pipelines. The lecture will cover methods to seamlessly integrate security tools that automatically scan for vulnerabilities as part of the build process, thereby ensuring that security is a core component of the development lifecycle. Strategies for configuring automated gates that can block or flag builds based on the severity of detected issues will be discussed, ensuring that only secure code progresses through the pipeline.
Triaging Issues with Automation:
This segment addresses how automation can be leveraged to intelligently triage and prioritize security issues. It will cover technologies and methodologies for automatically assessing the context and potential impact of vulnerabilities, facilitating quicker and more accurate decision-making. The use of automated alerting and reporting mechanisms to ensure the right stakeholders are informed in a timely manner will also be discussed.
Identifying Ownership Automatically:
Automating the process of identifying who owns the responsibility for fixing specific security issues is critical for efficient remediation. This part of the lecture will explore tools and practices for mapping vulnerabilities to code owners, leveraging version control and project management tools.
Three Tips to Scale the Shift Left Program:
Finally, the lecture will offer three practical tips for organizations looking to scale their Shift Left security programs. These will include recommendations on fostering a security culture within development teams, employing DevSecOps principles to integrate security throughout the development
9 Ways Pastors Will Use AI Everyday By 2029
These future use cases are only a handful of the many many options generative AI is providing pastors and leaders everywhere. If you learn how AI might enhance and support your ministry, you'll enter into a world that's full of hope for the Gospel.
Learn more at http://www.AIforChurchLeaders.com and http://www.churchtechtoday.com
Chapter 3 of ISTQB Foundation 2018 syllabus with sample questions. Answers about what is static testing, what is review, types of review, informal review, walkthrough, technical review, inspection.
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.
Quality Patents: Patents That Stand the Test of TimeAurora Consulting
Is your patent a vanity piece of paper for your office wall? Or is it a reliable, defendable, assertable, property right? The difference is often quality.
Is your patent simply a transactional cost and a large pile of legal bills for your startup? Or is it a leverageable asset worthy of attracting precious investment dollars, worth its cost in multiples of valuation? The difference is often quality.
Is your patent application only good enough to get through the examination process? Or has it been crafted to stand the tests of time and varied audiences if you later need to assert that document against an infringer, find yourself litigating with it in an Article 3 Court at the hands of a judge and jury, God forbid, end up having to defend its validity at the PTAB, or even needing to use it to block pirated imports at the International Trade Commission? The difference is often quality.
Quality will be our focus for a good chunk of the remainder of this season. What goes into a quality patent, and where possible, how do you get it without breaking the bank?
** Episode Overview **
In this first episode of our quality series, Kristen Hansen and the panel discuss:
⦿ What do we mean when we say patent quality?
⦿ Why is patent quality important?
⦿ How to balance quality and budget
⦿ The importance of searching, continuations, and draftsperson domain expertise
⦿ Very practical tips, tricks, examples, and Kristen’s Musts for drafting quality applications
https://www.aurorapatents.com/patently-strategic-podcast.html
Database Management Myths for DevelopersJohn Sterrett
Myths, Mistakes, and Lessons learned about Managing SQL Server databases. We also focus on automating and validating your critical database management tasks.
Test Management as Chapter 5 of ISTQB Foundation. Topics covered are Test Organization, Test Planning and Estimation, Test Monitoring and Control, Test Execution Schedule, Test Strategy, Risk Management, Defect Management
How to Improve Your Ability to Solve Complex Performance ProblemsScyllaDB
This talk is really about problem solving. It’s about how we think about problems and how we resolve those problems in a deeply technical context. The main goal of the talk is the relay the lessons learned from a couple of decades working with and observing some of the best performance troubleshooters in the world.
The talk will be broken into 3 main parts.
1. Explain the basic process we must go through to solve a complex performance problem
2. Discuss some of the main factors that can inhibit our efforts
3. Discuss some of the techniques we can apply to improve our chances, including an almost fool proof method to reach a successful outcome
Specific technical examples from large enterprise customers using relational databases (Oracle primarily) will be used to illustrate the concepts.
3. “Has it loaded yet?”
http://www.flickr.com/photos/kindofindie/4099768084
4. Our perception of response time
Instant
Seamless Yawn!
100ms 1s 10s
3s - Recommended 6.5s - Alexa 2000
Load Time Fall 2012
Response Time in Man-computer Conversational Transactions
Robert B. Miller, 1968
5. “50% more concentration when using
badly performing web sites”
Foviance
http://www.flickr.com/photos/yourdon/3366991042
6. Effect of delay on abandonment rate...
Abandonment rate over 200+ sites / 177+ million page views over 2 weeks - http://www.measureworks.nl / Gomez
22. Over 80% of page load time is on front-end
Backend
news.bbc.co.uk
Frontend
ebay.co.uk
debenhams.co.uk
direct.gov.uk
amazon.co.uk
mumsnet.com
guardian.co.uk
0 1 2 3 4 5
Measured via residential ADSL line using Google Chrome
24. Bandwidth (often) isn’t the bottleneck
2.0
1.5
1.0
0.5
0s 5s 10s
news.bbc.co.uk tested via webpagetest.org throttled at 1.5Mbps
(bursts over 1.5Mbps are artefact of testing)
26. Visualising TCP
Carlos Bueno (@archivd) https://vimeo.com/14439742
27. Impact of Latency
4
3
Page Load Time (s)
2
1
0 20 40 60 80 100 120 140 160 180 200 220 240
Round Trip Time (ms)
28. Minimum round trips to download a file
(TCP Segments)
285kB
214kB
143kB
71kB
Size
1 2 3 4 5 6 7 8 9 10 11
Round Trips TCP and the Lower Bound of Web Performance
John Rauser
29. Latency is Our Biggest Enemy
“In 2012, the average worldwide RTT to Google is still
~100ms, and ~50-60ms within the US.”
“we are looking at 100-1000ms RTT range on mobile”
Ilya Grigorik
http://www.igvita.com/2012/07/19/latency-the-new-web-performance-bottleneck/
30. 3G Radio Resource Control
Idle for 12s
IDLE CELL_FACH
1s delay
1-2s delay!
CELL_DCH Idle for 5s
Exact timings vary and depend on carrier NOT device
http://web.eecs.umich.edu/~fengqian/paper/3g_imc10.pdf
39. Use “Right-sized” Images
http://www.flickr.com/photos/emzee/139794246
Standards support (picture? srcset?) is coming but unclear when!
Meanwhile services such as sencha.io, resrc.it and JS libraries -
picturefill.js, foresight.js can help.
41. Parallel Downloads
news.bbcimg.co.uk
static.bbc.co.uk
Domain Sharding increases number of parallel downloads but…
…more connections may not be a good idea on mobile
…may also interfere with multiplexing in protocols like SPDY
42. Get the <head> straight
<!doctype html>
<html>
<head>
CSS before JS
<meta charset="utf-8"> Ideally one file*
<title>This is my title<title>
<link rel="stylesheet" href="styles.css" type="text/css" />
<script src="script.js"></script>
.
. Only JS needed
. during page load
</head>
* Depends on size and whether major / minor breakpoints used
43. Load remaining Javascript late as possible
.
.
.
<script src="restofscript.js"></script>
</body>
</html>
One file or many?
(Depends on size)
Script loaders can help but scripts aren’t discoverable by pre-fetcher
44. The Script Tag
<script src=″…″></script>
Until the script has executed, the rendering of
all elements below is blocked!
45. “Virgin Media Broadband ISP Users
Affected by Website Routing Woes”
ISP Review, May 26, 2012
Customer jcmm33 said:
“Same issue here as well, been like this all day. Sites like
autotrader.co.uk don’t appear to be accessible, others like
the telegraph.co.uk are waiting on other components to
download (content from sites like cg-global.maxymiser.com,
pixel.quantserve.com).”
http://www.ispreview.co.uk/index.php/2012/05/uk-virgin-media-broadband-isp-users-affected-by-website-routing-woes.html
46. Impact on The Telegraph…
Same issue affected many other sites http://bit.ly/Ncy7Rd
47. Load Third Party scripts asynchronously
<script type="text/javascript">
function() {
var js = document.createElement('script');
js.async = true;
js.src = 'myscript.js';
var e = document.getElementsByTagName('script')[0];
e.parentNode.insertBefore(js, first);
})();
</script>
Or use a script loader - labjs, requirejs, yepnope etc.
48. Lots of factors to think about...
http://www.flickr.com/photos/corneveaux/3248566797
49. Don’t have to do it all by hand
http://www.flickr.com/photos/simeon_barkas/2557059247