Web performance optimisation has been gaining ground and is slowly getting more of its deserved recognition. Now that we’ve learned to recognise this integral part of user experience and are approaching HTTP/2 as our new protocol of choice, some of our existing web performance best practices will turn into the new anti-patterns.
Talk slides from FEDay Conference in Guangzhou, China on 19/03/2016.
1. The document describes the common HTTP methods used to retrieve or send data over the web, including GET, HEAD, POST, PUT, DELETE, CONNECT, OPTIONS, and TRACE.
2. GET is used to retrieve a resource, HEAD is like GET but only returns headers, and POST sends data to a server like form data or file uploads.
3. PUT replaces a resource with uploaded content, DELETE removes a resource, and CONNECT establishes a tunnel. OPTIONS returns supported methods and TRACE echoes a request for debugging.
A technical description of http2, including background of HTTP what's been problematic with it and how http2 and its features improves the web.
See the "http2 explained" document with the complete transcript and more: http://daniel.haxx.se/http2/
(Updated version to slides shown on April 13th, 2016)
HTTP/2 aims to address issues with HTTP/1.x such as head-of-line blocking and wasted bandwidth through duplicate requests. It uses a binary format for multiplexing requests, server push, header compression, stream prioritization and flow control. Major browsers now support HTTP/2 over TLS, though server implementations are still in development. While preserving the HTTP/1.1 API, HTTP/2 provides advantages like cheaper requests and more efficient use of network resources and server capacity.
Altitude San Francisco 2018: Programming the EdgeFastly
Programming the edge
Second floor
Andrew Betts
Principal Developer Advocate, Fastly
Hide abstract
Through our support for running your own code on our edge servers, Fastly's network offers you a platform of unparalleled speed, reliability and efficiency to which you can delegate a surprising amount of logic that has traditionally been in the application layer. In this workshop, you'll implement a series of advanced edge solutions, and learn how to apply these patterns to your own applications to reduce your origin load, dramatically improve performance, and make your applications more secure.
HTTP by Hand: Exploring HTTP/1.0, 1.1 and 2.0Cory Forsyth
This document summarizes the evolution of HTTP from versions 0.9 to 2. It discusses key aspects of HTTP/1.0 and HTTP/1.1 such as persistent connections and pipelining. It also covers how these features were abused to optimize page load performance. Finally, it provides an overview of HTTP/2 and how it differs from previous versions through the use of binary format, header compression, and multiplexing requests over a single TCP connection.
The document discusses REST API design principles and best practices. It begins by providing examples of RESTful API requests and responses. It then covers REST concepts like resources, verbs, hypermedia, content negotiation, and representation formats. The document advocates for designing APIs that are self-documenting through hypermedia and embedding links to allow discovery of available state transitions and actions. It also discusses balancing REST purism with pragmatic design choices and notes that many popular APIs are not purely RESTful but are still well-designed.
The document introduces HTTP/2 and discusses limitations of HTTP 1.1 including head of line blocking, TCP slow start, and latency issues. It describes key features of HTTP/2 such as multiplexing requests over a single TCP connection, header compression, and server push to reduce page load times. The presentation includes demos of HTTP/2 in Chrome dev tools and Wireshark to troubleshoot HTTP/2 connections.
This document summarizes the history and development of HTTP/2. It discusses the limitations of HTTP/1 that HTTP/2 aims to address, such as head-of-line blocking. The key features of HTTP/2 are described, including multiplexing, priority, header compression, and server push. The document also covers topics like TLS, QUIC, and tools for debugging HTTP/2 implementations.
HTTP 1.1, which is the backbone of pretty much everything we’ve been using on the Internet, has been around for over 15 years. Recently the HTTP 2.0 specification has been completed and gradually application servers will start supporting it. It does make one wonder though: why change if something has been working for so long. In this talk we’ll examine the shortcomings of HTTP 1.1 and how 2.0 intends to address those. We’ll see what we need to know and how it’s going to affect our existing applications, and future ones.
Daniel Stenberg gave a presentation on the current status of HTTP/2. He discussed how HTTP usage has grown significantly, leading to slower page loads. HTTP/1.1 workarounds like concatenation and sharding add complexity. HTTP/2 aims to address these issues through features like multiplexed streams, header compression, and server push while maintaining backwards compatibility. Major browsers now support HTTP/2, but it currently only makes up a small percentage of traffic. Widespread adoption will take time as developers adjust practices.
The document discusses HTTP (Hypertext Transfer Protocol), which is the foundation for web technologies like REST, AJAX, and HTTPS. It explains that HTTP is the language browsers use to communicate with web servers and carry most web traffic. The document provides examples of using tools like Charles, browsers like Chrome, and cURL to view HTTP requests and responses and experiment with different HTTP methods, status codes, and headers.
RFC 7540 was ratified over 2 years ago and, today, all major browsers, servers, and CDNs support the next generation of HTTP. Just over a year ago, at Velocity (https://www.slideshare.net/Fastly/http2-what-no-one-is-telling-you), we discussed the protocol, looked at some real world implications of its deployment and use, and what realistic expectations we should have from its use.
Now that adoption is ramped up and the protocol is being regularly used on the Internet, it's a good time to revisit the protocol and its deployment. Has it evolved? Have we learned anything? Are all the features providing the benefits we were expecting? What's next?
In this session, we'll review protocol basics and try to answer some of these questions based on real-world use of it. We'll dig into the core features like interaction with TCP, server push, priorities and dependencies, and HPACK. We'll look at these features through the lens of experience and see if good practice patterns have emerged. We'll also review available tools and discuss what protocol enhancements are in the near and not-so-near horizon.
Web Performance Automation - NY Web Performance MeetupStrangeloop
The document discusses performance automation, including:
- Basic terminology like waterfall charts and how they break down page load times.
- A case study showing how automation identified issues like too many connections, bytes, and roundtrips on a site and incrementally improved performance through techniques like caching, CDNs, minification, and domain sharding.
- The history and evolution of the performance automation market from delivery to more advanced transformation tools. Challenges include supporting new technologies and standardizing measurements. Speed remains an important opportunity area.
Developers choose HTTP for its ubiquity. HTTP's semantics are cherry-picked or embraced in the myriad of apis we develop and consume. Efficiency discussions are commonplace: Does this design imply N+1 requests? Should we denormalize the model? How do consumers discover changes in state? How many connections are needed to effectively use this api?
Meanwhile, HTTP 1.1 is a choice, as opposed to constant. SPDY and HTTP/2 implementations surface, simultaneously retaining semantics and dramatically changing performance implications. We can choose treat these new protocols as more efficient versions HTTP 1.1 or buy into new patterns such as server-side push.
This session walks you through these topics via an open source project from Square called okhttp. You'll understand how okhttp addresses portability so that you can develop against something as familiar as java's HTTPUrlConnection. We'll review how to use new protocol features and constraints to keep in mind along the way. You'll learn how to sandbox ideas with okhttp's mock server, so that you can begin experimenting with SPDY and HTTP/2 today!
The document discusses key concepts for operating a web site, including TCP/IP, HTTP, and web data formats. It covers TCP/IP concepts like IP addresses and ports, HTTP versions and methods, and web data formats like HTML, XHTML, and XML. Sample HTTP requests are also provided to illustrate HTTP methods and requests/responses.
HTTP is one of the most widely used protocols in the world.
The version of HTTP 1.1, used to this day, was developed and described 18 years ago - 1999.
With the increasing complexity of web applications, the capabilities of HTTP 1.1 are already insufficient to provide increased demands on performance and responsiveness.
So in order to meet new requirements, HTTP must evolve. HTTP 2.0 is designed to make web applications faster, simple and reliable.
In this report I will tell about
- drawbacks of HTTP 1.1 and why we need a new version of HTTP.
- which advantages HTTP/2 offers in comparison with the previous version?
- how the new protocol affected the new version of SERVLET 4.0 and how we can use it.
What we can learn from CDNs about Web Development, Deployment, and PerformanceFastly
CDNs provide caching and delivery of web content but are often misused. CDNs can cache more dynamic content than typically done and improve performance. Precise measurement is still difficult, such as determining cache hit rates and impacts of memory versus disk hits. Overall, CDNs have more potential for optimization and caching improvements remain an ongoing challenge.
Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1yKnuxS.
Omer Shapira introduces HTTP/2 (and SPDY), exploring the impact the protocol has on application design, and telling the story of LinkedIn adopting SPDY on its network infrastructure. Filmed at qconsf.com.
Omer Shapira is an engineering manager at LinkedIn. He and his team are building scalable, low-latency traffic infrastructure to keep LinkedIn site fast.
The web has dramatically evolved over the last 20+ years, yet HTTP - the workhorse of the Web - has not. Web developers have worked around HTTP's limitations, but:
--> Performance still falls short of full bandwidth utilization
--> Web design and maintenance are more complex
--> Resource consumption increases for client and server
--> Cacheability of resources suffers
HTTP/2 attempts to solve many of the shortcomings and inflexibilities of HTTP/1.1
[White Paper] Innovations in Mobile Content Delivery: Avoiding the Great Mobi...Cotendo
Learn about the technology limitations killing the performance of mobile websites and mobile apps, plus how innovations in mobile content delivery networks (CDNs) can transform users’ experience of the mobile Web. Understand why Round Trip Time (RTT) is the biggest factor hindering mobile performance for end users, and learn why it’s essential to take a three-prong approach to improving mobile content delivery: accelerating content at the network, content and logic levels. This concise industry brief about the mobile cloud will get you up to speed on key factors and best practices in optimizing mobile performance.
Some of the newer CDN technologies can address the logic level in a number of innovative ways. First, they can more intelligently cache information close to end users with mobile devices, and use the location as a cache-key. So, for example, a weather site can, with this type of logic, cache appropriate detailed weather information for a user in the CDN based on their initial GPS contact point. This weather data can be later served to other users located a few blocks away, eliminating the need for additional round trips.
This document summarizes a presentation on high performance mobile web. The presentation covers:
- Delivering fast mobile experiences by making fewer HTTP requests, using CDNs, browser prefetching, and other techniques.
- Measuring web performance using Navigation Timing, Resource Timing, custom timing marks, and tools like WebPagetest and Google Analytics.
- Typical mobile network performance statistics like average latency, download speeds, and how these numbers impact page load times.
The document discusses HTTP/2 and its implications for Java. It begins with an introduction to HTTP/2 and why it was created, noting limitations of HTTP/1.1 in handling modern web pages with many dependent resources. The document then covers specifics of the HTTP/2 protocol, and how it addresses issues like head-of-line blocking. It discusses how HTTP/2 is being adopted by browsers and considers impacts and integration of HTTP/2 with Java SE and Java EE technologies.
HTTP/2 is an updated protocol that improves upon HTTP/1.1 by allowing multiple requests to be sent simultaneously over a single TCP connection using multiplexing and header compression. It reduces latency compared to HTTP/1.1 by fixing the head-of-line blocking problem and prioritizing important requests. Key features of HTTP/2 evolved from the SPDY protocol and include multiplexing, header compression, prioritization, and protocol negotiation.
Http2 is here! And why the web needs itIndicThreads
The document summarizes the evolution of HTTP from versions 0.9 to 2.0. It outlines the limitations of HTTP/1.1 for modern web pages with many dependent resources. HTTP/2 aims to address these limitations through features like multiplexing, header compression, server push and priority to reduce latency. It discusses implementations of HTTP/2 and the impact on developers. The document also briefly mentions upcoming protocols like QUIC that build on HTTP/2 to further optimize performance.
This document compares the HTTP and SPDY protocols. It finds that SPDY significantly reduces latency compared to HTTP, especially on mobile devices. SPDY allows for multiplexed requests, prioritized requests, and compressed headers over a single TCP connection. Experiments show SPDY was 27-60% faster than HTTP without SSL and 39-55% faster than HTTP with SSL. However, SPDY latency could still be improved by addressing issues like bandwidth efficiency, SSL challenges, and packet loss recovery.
- HTTP/2 aims to reduce HTTP response times by improving bandwidth efficiency and reducing the number of connections and messages needed. It allows requests to be multiplexed over a single connection.
- While it can't reduce latency at the packet level, it aims to reduce overall response times through features like header compression, server push, and priority hints.
- HTTP/2 is currently supported by major browsers and servers. Implementations so far show response time reductions of 5-60% compared to HTTP/1.1.
The document discusses the changes from HTTP/1.1 to HTTP/2, including multiplexing, server push, and priority. It notes that HTTP/2 was based on Google's SPDY experiment and aims to improve web performance. While HTTP/2 benefits some sites more than others, overall it helps reduce latency by allowing multiple requests over a single connection through header compression and other methods. However, factors like network latency still ultimately limit performance.
Art and Science of Web Sites Performance: A Front-end ApproachJiang Zhu
People love fast web sites, but up until now developers have been focusing on the wrong area. Network (TCP, buffers, routing) performance and Backend (web server, database, etc.) performance are important for reducing hardware costs and improving efficiency, but for most pages 80% of the load time is spent on the frontend (HTML, CSS, JavaScript, images, iframes, and others). We will talk about the best practices for making web pages faster, provide case study from top web site, and introduce the tools we use for researching performance. In addition to know how to improve web performance, we will also try to gain an understanding of the fundamentals of how the Internet works including DNS, HTTP, and browsers. This talks was given as an Educational Series called Fog Computing Reading Group at Cisco Advanced Architecture and Research. The content is derived from the materials by Steven Sounders (Google/Stanford), Collin Jackson (Stanford/CMU) and Daniel Austin (eBay).
This document summarizes a thesis that explores using peer-to-peer (P2P) techniques to more efficiently deliver web content. It presents a research platform called DCDN that uses WebRTC to enable P2P content sharing between browsers without plugins. The thesis evaluates different configurations and finds P2P works best for high-definition video and audio due to roadblocks like JavaScript limitations and user behavior. Emerging technologies like Service Workers may help overcome obstacles to expand P2P's uses.
Delivering High Performance Websites with NGINXNGINX, Inc.
NGINX Plus is an easy-to-install, proven software solution to deliver your sites and applications through state-of-the-art intelligent load balancing and high performance acceleration. Improve your servers’ performance, scalability, and reliability with application delivery from NGINX Plus.
NGINX Plus significantly increases application performance during periods of high load with its caching, HTTP connection processing, and efficient offloading of traffic from slow networks. NGINX Plus offers enterprise application load balancing, sophisticated health checks, and more, to balance workloads and avoid user-visible errors.
Check out this webinar to:
* Learn why web performance matters more than ever, in the face of growing application complexity and traffic volumes
* Get the lowdown on the performance challenges of HTTP, and why the real world is so different to a development environment
* Understand why NGINX and NGINX Plus are such popular solutions for mitigating these problems and restoring peak performance
* Look at some real-world deployment examples of accelerating traffic in complex scenarios
Dynamic Content Acceleration: Lightning Fast Web Apps with Amazon CloudFront ...Amazon Web Services
Traditionally, content delivery networks (CDNs) were known to accelerate static content. Amazon CloudFront has come a long way and now supports delivery of entire websites that include dynamic and static content. In this session, we introduce you to CloudFront’s dynamic delivery features that help improve the performance, scalability, and availability of your website while helping you lower your costs. We talk about architectural patterns such as SSL termination, close proximity connection termination, origin offload with keep-alive connections, and last-mile latency improvement. Also learn how to take advantage of Amazon Route 53's health check, automatic failover, and latency-based routing to build highly available web apps on AWS.
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
Similar to Web Performance in the Age of HTTP/2 - FEDay Conference, Guangzhou, China 19/03/2016 (20)
The Untold Benefits of Ethical Design - Topconf Tallinn 2018Holger Bartel
Product design can go wrong and affect users negatively. How do your users feel using your product? What’s the impact that you cause? Can we build better products if we follow certain standards or principles?
This talk will explore how to better care about users and improve their experience by taking a more ethical approach. Most importantly, this talk will hopefully be an inspiration, question the status quo and help us build for a better future web.
The Untold Benefits of Ethical Design - Coldfront 2018, CopenhagenHolger Bartel
The document discusses the importance of ethical design. It argues that designers should focus on creating products that benefit users and society, consider how designs may negatively impact people, and prioritize data privacy and security. The document also stresses that designers have a responsibility to treat users well and should reconsider approaches that do not respect people or could enable harm. Overall, it promotes designing with good intent and continual improvement to help build a better future internet.
The Untold Benefits of Ethical Design - Web Directions Summit 2018, SydneyHolger Bartel
Product design can go wrong and affect users negatively. How do your users feel using your product? What’s the impact that you cause? Can we build better products if we follow certain standards or principles?
This talk will explore how to better care about users and improve their experience by taking a more ethical approach. Most importantly, this talk will hopefully be an inspiration, question the status quo and help us build for a better future web.
Web Performance in the Age of HTTP2 - Topconf Tallinn 2016 - Holger BartelHolger Bartel
Web performance optimisation has been gaining ground and is slowly getting more of its deserved recognition.
Nevertheless, much of our time on the web is still used up by waiting. To decrease our wait time and improve the web’s overall performance, this integral part of user experience needs further promotion.
Waiting and the perception of time itself, is reason enough to explore some of the psychological effects time has on our users, too.
Passing time also plays a big role in the evolution of technologies. Through the history of HTTP we have reached the latest version as HTTP/2, which will turn some of our existing web performance best practices on their head and into the new anti-patterns of today.
Form Function Class 6, Manila, Philippines 14/11/2015Holger Bartel
Sweating Details - Slides from my talk at Form Function Class 6 in Manila Philippines on Nov 14th, 2015.
This talk is about sweating details and how small tweaks and changes can make a big difference in any of the web design stages. From optimising the process, via UX and design all the way to performance, this talk covers possible tweaks and recommendations with some practical examples to improve the overall experience of our products.
These are the slides from my talk "Your WebPerf Sucks" at HK CodeConf 2015 (http://hongkong.codeconf.io) at Science Park in Hong Kong, October 24th.
Web Performance is an important aspect of building for the web and this talk highlights different aspects of what is important and what can be done to improve web performance and build faster sites. While mentioning different aspects of possible improvements, the main focus lies on optimising the critical rendering path to get pages on the screen faster and what tools can help to do so.
Front End Tooling and Performance - Codeaholics HK 2015Holger Bartel
Front End Tooling and Performance is a case study on what I used to make missedin-hkg.com load in less than 1000ms and optimise front end performance in various ways.
This talk has been held at the Codeaholics Meetup in Hong Kong on 08. April 2015.
The document discusses responsive web design and some best practices. It notes that responsive design is more than just fluid grids, flexible images, and media queries - it also requires considering architecture, performance, font sizing, breakpoints, image optimization, and more. The document provides tips on using relative units like ems and rems for font sizing, organizing media queries, selecting classes, and testing responsive sites.
Front End Best Practices: A Selection of Best Practices, Tips, Tricks & Good Advice For Today’s Front End Development. Practices mentioned in this presentation range from basic principles to more advanced tools and techniques. By Holger Bartel for WomenWhoCodeHK 23/07/2014
180 Degrees East - Insights into the Mobile Web in Asia, with a closer look on the market in Hong Kong and China, its infrastructure, different devices, OS fragmentation and what it means for Responsive Web Design, App Development as well as Performance & GeoPerformance.
My slides from my talk at Webshaped 2013 in Helsinki, Finland. A look at the Asian mobile market, the mobile web infrastructure, statistics and user behaviour in comparison to the western world, cultural differences and personal challenges encountered along the way.
180 Degrees East at Front Trends 2013, Warsaw, PolandHolger Bartel
Slides from my talk '180 Degrees East' at Front Trends 2013, Warsaw, Poland.
Insights on the Asian mobile & web market, statistics and user behaviour in comparison to the western world, cultural differences and personal challenges encountered along the way.
Open Device Labs for A Better User Experience (Mobilliance, Hong Kong)Holger Bartel
Slides from a short talk I did on why Open Device Lab are important to improve User Experience, including a few stats on the ever growing mobile web. Mobilliance at The Hive in Hong Kong.
Responsive Web Design & Workflows for Todays Web (THE UX-MEN at The Hive, Hon...Holger Bartel
A primer on responsive design, various aspects on this technique, various examples, challenges and best practices in form of a case study of a past project as well as considerations and lessons learned.
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
Best Practices for Effectively Running dbt in Airflow.pdfTatiana Al-Chueyr
As a popular open-source library for analytics engineering, dbt is often used in combination with Airflow. Orchestrating and executing dbt models as DAGs ensures an additional layer of control over tasks, observability, and provides a reliable, scalable environment to run dbt models.
This webinar will cover a step-by-step guide to Cosmos, an open source package from Astronomer that helps you easily run your dbt Core projects as Airflow DAGs and Task Groups, all with just a few lines of code. We’ll walk through:
- Standard ways of running dbt (and when to utilize other methods)
- How Cosmos can be used to run and visualize your dbt projects in Airflow
- Common challenges and how to address them, including performance, dependency conflicts, and more
- How running dbt projects in Airflow helps with cost optimization
Webinar given on 9 July 2024
Understanding Insider Security Threats: Types, Examples, Effects, and Mitigat...Bert Blevins
Today’s digitally connected world presents a wide range of security challenges for enterprises. Insider security threats are particularly noteworthy because they have the potential to cause significant harm. Unlike external threats, insider risks originate from within the company, making them more subtle and challenging to identify. This blog aims to provide a comprehensive understanding of insider security threats, including their types, examples, effects, and mitigation techniques.
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.
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.
UiPath Community Day Kraków: Devs4Devs ConferenceUiPathCommunity
We are honored to launch and host this event for our UiPath Polish Community, with the help of our partners - Proservartner!
We certainly hope we have managed to spike your interest in the subjects to be presented and the incredible networking opportunities at hand, too!
Check out our proposed agenda below 👇👇
08:30 ☕ Welcome coffee (30')
09:00 Opening note/ Intro to UiPath Community (10')
Cristina Vidu, Global Manager, Marketing Community @UiPath
Dawid Kot, Digital Transformation Lead @Proservartner
09:10 Cloud migration - Proservartner & DOVISTA case study (30')
Marcin Drozdowski, Automation CoE Manager @DOVISTA
Pawel Kamiński, RPA developer @DOVISTA
Mikolaj Zielinski, UiPath MVP, Senior Solutions Engineer @Proservartner
09:40 From bottlenecks to breakthroughs: Citizen Development in action (25')
Pawel Poplawski, Director, Improvement and Automation @McCormick & Company
Michał Cieślak, Senior Manager, Automation Programs @McCormick & Company
10:05 Next-level bots: API integration in UiPath Studio (30')
Mikolaj Zielinski, UiPath MVP, Senior Solutions Engineer @Proservartner
10:35 ☕ Coffee Break (15')
10:50 Document Understanding with my RPA Companion (45')
Ewa Gruszka, Enterprise Sales Specialist, AI & ML @UiPath
11:35 Power up your Robots: GenAI and GPT in REFramework (45')
Krzysztof Karaszewski, Global RPA Product Manager
12:20 🍕 Lunch Break (1hr)
13:20 From Concept to Quality: UiPath Test Suite for AI-powered Knowledge Bots (30')
Kamil Miśko, UiPath MVP, Senior RPA Developer @Zurich Insurance
13:50 Communications Mining - focus on AI capabilities (30')
Thomasz Wierzbicki, Business Analyst @Office Samurai
14:20 Polish MVP panel: Insights on MVP award achievements and career profiling
The DealBook is our annual overview of the Ukrainian tech investment industry. This edition comprehensively covers the full year 2023 and the first deals of 2024.
7 Most Powerful Solar Storms in the History of Earth.pdfEnterprise Wired
Solar Storms (Geo Magnetic Storms) are the motion of accelerated charged particles in the solar environment with high velocities due to the coronal mass ejection (CME).
論文紹介:A Systematic Survey of Prompt Engineering on Vision-Language Foundation ...Toru Tamaki
Jindong Gu, Zhen Han, Shuo Chen, Ahmad Beirami, Bailan He, Gengyuan Zhang, Ruotong Liao, Yao Qin, Volker Tresp, Philip Torr "A Systematic Survey of Prompt Engineering on Vision-Language Foundation Models" arXiv2023
https://arxiv.org/abs/2307.12980
Implementations of Fused Deposition Modeling in real worldEmerging Tech
The presentation showcases the diverse real-world applications of Fused Deposition Modeling (FDM) across multiple industries:
1. **Manufacturing**: FDM is utilized in manufacturing for rapid prototyping, creating custom tools and fixtures, and producing functional end-use parts. Companies leverage its cost-effectiveness and flexibility to streamline production processes.
2. **Medical**: In the medical field, FDM is used to create patient-specific anatomical models, surgical guides, and prosthetics. Its ability to produce precise and biocompatible parts supports advancements in personalized healthcare solutions.
3. **Education**: FDM plays a crucial role in education by enabling students to learn about design and engineering through hands-on 3D printing projects. It promotes innovation and practical skill development in STEM disciplines.
4. **Science**: Researchers use FDM to prototype equipment for scientific experiments, build custom laboratory tools, and create models for visualization and testing purposes. It facilitates rapid iteration and customization in scientific endeavors.
5. **Automotive**: Automotive manufacturers employ FDM for prototyping vehicle components, tooling for assembly lines, and customized parts. It speeds up the design validation process and enhances efficiency in automotive engineering.
6. **Consumer Electronics**: FDM is utilized in consumer electronics for designing and prototyping product enclosures, casings, and internal components. It enables rapid iteration and customization to meet evolving consumer demands.
7. **Robotics**: Robotics engineers leverage FDM to prototype robot parts, create lightweight and durable components, and customize robot designs for specific applications. It supports innovation and optimization in robotic systems.
8. **Aerospace**: In aerospace, FDM is used to manufacture lightweight parts, complex geometries, and prototypes of aircraft components. It contributes to cost reduction, faster production cycles, and weight savings in aerospace engineering.
9. **Architecture**: Architects utilize FDM for creating detailed architectural models, prototypes of building components, and intricate designs. It aids in visualizing concepts, testing structural integrity, and communicating design ideas effectively.
Each industry example demonstrates how FDM enhances innovation, accelerates product development, and addresses specific challenges through advanced manufacturing capabilities.
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
RPA In Healthcare Benefits, Use Case, Trend And Challenges 2024.pptxSynapseIndia
Your comprehensive guide to RPA in healthcare for 2024. Explore the benefits, use cases, and emerging trends of robotic process automation. Understand the challenges and prepare for the future of healthcare automation
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)
Transcript: Details of description part II: Describing images in practice - T...BookNet 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 slides: 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.
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.
16. Users expect ~2-3 seconds to load a site…
This is a user’s definition of ‘fast’
And today, we’re even aiming to deliver something faster
User Expectations
17. 50% of people say they'll abandon a page that takes
longer than 4 seconds to load
User Expectations
18. Depending on a users location and infrastructure it
might take longer
More than 8-10 seconds of load time for sure is pushing
it and people will not wait
User Expectations
19. Delay User perception
0–100 ms Instant
100–300 ms Small perceptible delay
300–1000 ms Machine is working
1,000+ ms Likely mental context switch
10,000+ ms Task is abandoned
Source
20. The unofficial rule of thumb in the web
performance community:
Render pages, or at the very least provide
visual feedback, in under 250 milliseconds to
keep the user engaged!
Source
23. Speeding up a
fundraising site by
60% increased
donations by 14%.
— Obama Campaign
Adding half a second to a
search results page can
decrease traffic and ad
revenues by 20%
— Google
Every additional 100
milliseconds of load
time decreased
sales by 1%.
— Amazon
40% of surveyed online
shoppers will abandon a
page that takes more
than 3 seconds to load.
— Akamai
36. Waiting for DOM and CSSOM to build the render tree.
Render tree contains nodes to render the page.
Layout computes the exact position and size.
Paint turns the render tree into pixels on screen.
Render-Tree Construction,
Layout & Paint
Source
38. The parser has to stop for scripts before continuing to
parse HTML.
JavaScript can query and modify DOM and CSSOM.
JavaScript blocks DOM construction unless
explicitly declared as async.
Render Blocking JavaScript
Source
39. Every request fetched inside of HEAD, will postpone
the rendering of the page
Loading JavaScript
Source
43. Minimize the number of critical resources.
Minimize the number of critical bytes.
Minimize the critical path length.
A critical resource is a resource that can block
initial rendering of a page.
Source
52. To reduce the load on the server, HTTP/1.1’s
approach was to limit its TCP connections
“A single-user client should not maintain more
than 2 connections with any server or proxy.”
In real life, browsers hold ~6 TCP connections
simultaneously per origin.
53. More Bandwidth Doesn’t Make a Big Difference
An increase from 5Mbps to 10Mbps results in a
disappointing 5% improvement in page load times.
Source
62. Multiplexing: allow concurrent requests
across a single TCP connection;
Allow browsers to prioritise assets so that
vital resources of a page could are sent first;
Compress and reduce HTTP headers;
Server push: A server can push important
resources to the browser before being asked
for them.
64. Networking protocol for low-latency transport
of content over the web.
Originally started out from the SPDY protocol,
now standardised as HTTP version 2.
65. • Multiplexing
• Compressed headers
• Asset Prioritisation & Dependencies
• Server Push
(saves the time it takes the client to ask for
the resources)
70. Google* uses secure connections as a ranking
signal, and browsers are starting to flag non-h ps
websites as ‘not secure’.
Some HTML5 APIs will also require secure
connections in the future (e.g. Geolocation).
* Baidu Analytics includes a site speed section, so they might follow this
trend in the future.
Leveraging additional benefits of SSL
75. This was a workaround for the lack of parallelism in
HTTP/1.x to reduce requests;
Combining multiple files into one and fetch with one
request.
Need to wait of the entire file/response to arrive
Concatenation of Files
76. • Structure code to only deliver what’s needed
• No need for additional build process steps
• Optimise caching policies depending on change
frequency of files
New!
Requests are cheap!
78. Thanks to the new multiplexing ability of HTTP/2
resources don’t need to be queued anymore.
Nevertheless, depending on the kind of image, and how
they are used, spriting can still be the be er option in
regards to compression and file size.
Image Sprites
79. Another workaround for the lack of parallelism in
HTTP/1.x
Besides increasing the file size of stylesheets etc., the
resource can’t be cached and asset re-use will create
unnecessary overhead
Prioritisation features of HTTP/2 can’t be used
Inline Images
80. And one more workaround for the lack of multiplexing
in HTTP/1.x
Browsers can handle ~6 connections per origin, but
domain sharding allows us to (theoretically) extend this
to an unlimited amount of connections.
Domain sharding will have a negative impact when
used with HTTP/2.
Domain Sharding
Source
!
81. HTTP1.x HTTP2
Reduce DNS lookups ✓ ✓
Reuse TCP connections ✓ ✓
Use a Content Delivery Network ✓ ✓
Minimize number of HTTP redirects ✓ ✓
Eliminate unnecessary request bytes ✓ ✓
Compress assets during transfer ✓ ✓
Cache resources on the client ✓ ✓
Eliminate unnecessary resources ✓ ✓
Apply domain sharding Revisit (max 2) Remove
Concatenate resources Careful & consider caching Remove
Inline resources Careful & consider caching Remove (Server Push)
Source
83. Make the move to TLS & add a secure
connection to your site
(This can be done at any time and brings some additional benefits, even without HTTP/2)
Make sure your server supports HTTP/2
(Confirm with your hosting provider, roll your own or use a HTTP/2 supporting CDN service)
84. Prepare your assets & adjust the build process
for HTTP/2
(Adjust to output the required files that best suit your needs and test your choices)
Check Analytics & confirm your user’s
browser support
(This could affect users with older browsers negatively, and check for majority support)
Implement your favourite HTTP/2 best
practices and adjust your caching policies
(Measure your performance before and a er the update and share your results with the world!!)