Understanding
•Download as PPT, PDF•
1 like•275 views
The document discusses server-induced latency in web servers like Flash and Apache. It identifies that blocking from filesystem operations is a major source of latency. Experiments show blocking causes median latencies to grow unexpectedly and "service inversion" where small requests are served after large ones. The paper proposes moving filesystem calls out of the server process to reduce blocking. This approach called "Flashpache" reduces Flash latency by 15x and Apache latency by 9x while maintaining scalability with increased load.
Report
Share
Report
Share
![Background – Web servers ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
A Definitive Guide to DNS Time To Live
This document provides an overview of DNS (Domain Name System) time to live (TTL) settings. It explains that TTL determines how long each step in the DNS resolution process will cache a DNS record. Typical TTL times range from 5 minutes to 7 days. It also discusses best practices for setting and changing TTLs, such as using a low TTL initially and then increasing it once changes have propagated. The document notes that the median TTL found in a study of the top 500 websites was 300 seconds.
Web Speed And Scalability
The document provides tips for building a scalable and high-performance website, including using caching, load balancing, and monitoring. It discusses horizontal and vertical scalability, and recommends planning, testing, and version control. Specific techniques mentioned include static content caching, Memcached, and the YSlow performance tool.
Startups to Scale
The author describes several steps they took to scale their early stage startup as traffic increased:
1) They initially misconfigured their web server and database to use too much RAM, slowing performance, but easily fixed it.
2) As traffic increased, keeping HTTP connections open for a long time ("keepalive") exhausted server resources, so they disabled it.
3) Caching database data and rendered HTML on disk with Perl's Cache::FileCache helped improve performance.
4) Switching from MySQL to flat file storage using Perl's Tie::File improved performance for small data. BerkeleyDB was even faster.
5) Separating static content like images onto a different server improved concurrency.
Boyan Ivanov - latency, the #1 metric of your cloud
No two clouds are the same. Yet the leading clouds all have one thing in common: they deliver on metrics, which matter to the customer. In this session we'll dissect leading clouds, to show why low latency is the thing that makes a cloud stand out.
ScalabilityAvailability
The document discusses several concepts related to building scalable and available systems, including:
- Scalability involves a system's ability to handle expected loads with acceptable performance and to grow easily when loads increase. This may involve scaling up using bigger/faster systems or scaling out across multiple systems.
- Availability is the goal of having a system operational 100% of the time, requiring redundancy so there are no single points of failure.
- Performance measures like response time and throughput relate to a system's scalability and capacity. Distributing load across redundant and partitioned components can help improve scalability and availability.
Lamp Stack Optimization
Mike Creuzer's presentation on LAMP optimization for the October, 2009 meeting of the Suburban Chicago PHP & Web Development Meetup
Amazon builder Library notes
This document summarizes notes from the Amazon Builders Library about designing distributed systems. It discusses techniques like avoiding one-way decisions, ensuring rollback safety during deployments, using local and external caches effectively, implementing health checkers, load shedding to avoid overload, avoiding queue backlogs, and instrumenting systems for observability. The Amazon Builders Library contains articles on best practices for building AWS applications that are performant, robust, and reliable.
How Time To First Byte (TTFB) Impacts Your Site’s Performance
Let’s all agree that your #website speed can be subject to many factors. While it’s hard to break down all of them, it’s still not impossible. In this context, one of the metrics you can try to interpret and improve is Time To First Byte (#TTFB).
Recommended
A Definitive Guide to DNS Time To Live
This document provides an overview of DNS (Domain Name System) time to live (TTL) settings. It explains that TTL determines how long each step in the DNS resolution process will cache a DNS record. Typical TTL times range from 5 minutes to 7 days. It also discusses best practices for setting and changing TTLs, such as using a low TTL initially and then increasing it once changes have propagated. The document notes that the median TTL found in a study of the top 500 websites was 300 seconds.
Web Speed And Scalability
The document provides tips for building a scalable and high-performance website, including using caching, load balancing, and monitoring. It discusses horizontal and vertical scalability, and recommends planning, testing, and version control. Specific techniques mentioned include static content caching, Memcached, and the YSlow performance tool.
Startups to Scale
The author describes several steps they took to scale their early stage startup as traffic increased:
1) They initially misconfigured their web server and database to use too much RAM, slowing performance, but easily fixed it.
2) As traffic increased, keeping HTTP connections open for a long time ("keepalive") exhausted server resources, so they disabled it.
3) Caching database data and rendered HTML on disk with Perl's Cache::FileCache helped improve performance.
4) Switching from MySQL to flat file storage using Perl's Tie::File improved performance for small data. BerkeleyDB was even faster.
5) Separating static content like images onto a different server improved concurrency.
Boyan Ivanov - latency, the #1 metric of your cloud
No two clouds are the same. Yet the leading clouds all have one thing in common: they deliver on metrics, which matter to the customer. In this session we'll dissect leading clouds, to show why low latency is the thing that makes a cloud stand out.
ScalabilityAvailability
The document discusses several concepts related to building scalable and available systems, including:
- Scalability involves a system's ability to handle expected loads with acceptable performance and to grow easily when loads increase. This may involve scaling up using bigger/faster systems or scaling out across multiple systems.
- Availability is the goal of having a system operational 100% of the time, requiring redundancy so there are no single points of failure.
- Performance measures like response time and throughput relate to a system's scalability and capacity. Distributing load across redundant and partitioned components can help improve scalability and availability.
Lamp Stack Optimization
Mike Creuzer's presentation on LAMP optimization for the October, 2009 meeting of the Suburban Chicago PHP & Web Development Meetup
Amazon builder Library notes
This document summarizes notes from the Amazon Builders Library about designing distributed systems. It discusses techniques like avoiding one-way decisions, ensuring rollback safety during deployments, using local and external caches effectively, implementing health checkers, load shedding to avoid overload, avoiding queue backlogs, and instrumenting systems for observability. The Amazon Builders Library contains articles on best practices for building AWS applications that are performant, robust, and reliable.
How Time To First Byte (TTFB) Impacts Your Site’s Performance
Let’s all agree that your #website speed can be subject to many factors. While it’s hard to break down all of them, it’s still not impossible. In this context, one of the metrics you can try to interpret and improve is Time To First Byte (#TTFB).
Fighting Spam With A Perimeter Mail System 20071108 Sasag
The document discusses moving to a tiered perimeter mail system to better fight spam. Some key points:
- Implement a tiered system with separate hardware for mail filtering services like greylisting, antivirus scanning, and spam tagging to improve scalability.
- Configure Postfix and supporting services like GLD greylisting and amavisd-new with ClamAV for antivirus to optimize performance and throughput.
- Use load testing tools like smtp-source and smtp-sink to validate the new system can handle expected mail loads before putting into production.
WordPress Powered by AMIMOTO HHVM
This document summarizes the results of performance tests between HHVM and PHP-FPM on Nginx. In a test with an increasing load from 0-300 clients over 1 minute, HHVM had a faster average response time of 1566ms compared to 3108ms for PHP-FPM. HHVM was also able to process more requests, with 386830 requests compared to 2637 for PHP-FPM. While HHVM had a slower response at higher loads, PHP-FPM became unusable and returned errors at 150-200 clients.
Cloudflare lower network latency = faster website loads
Lower network latency = faster website loads
This document discusses how lower network latency leads to faster website loads. It explains that round-trip time (RTT) measures the time for a network request to travel from one point to another and back. Faster protocols like TLS 1.3 can reduce RTT by eliminating handshake rounds. Content delivery networks (CDNs) also reduce latency by caching content closer to users worldwide. New routing technologies like Cloudflare's Argo can improve performance by up to 59% by choosing network paths based on real-time conditions instead of following indirect routes. Overall, the document emphasizes that lower latency is key to optimizing the user experience on the web.
RIPE 78: IPv6 reliability measurements
APNIC Chief Scientist Geoff Huston presents on the IPv6 reliability measurements at RIPE 78 in Reykjavík, Iceland from 20 to 24 May 2019.
Performance engineering
The document discusses various techniques for optimizing UI performance, including optimizing caching, minimizing round-trip times, minimizing request size, minimizing payload size, and optimizing browser rendering. Specific techniques mentioned include leveraging browser and proxy caching, minimizing DNS lookups and redirects, combining external JavaScript, minimizing cookie and request size, enabling gzip compression, and optimizing images. Profiling and heap analysis tools are also discussed for diagnosing backend performance issues.
Performance Tuning - Memory leaks, Thread deadlocks, JDK tools
How to identify memory leaks in java applications, thread contentions, using jdk in built tools to identify performance bottlenecks
Best Practices - PHP and the Oracle Database
Web application performance correlates with page views. Find out in this session how to maximize the performance of the OCI8 database extension to build fast, scalable web sites and attract users. Includes discussion of Oracle Database 11.2 and the upcoming PHP OCI8 1.4 extension.
Advanced off heap ipc
This document discusses advanced inter-process communication (IPC) techniques using off-heap memory in Java. It introduces OpenHFT, a company that develops low-latency software, and their open-source projects Chronicle and OpenHFT Collections that provide high-performance IPC and embedded data stores. It then discusses problems with on-heap memory and solutions using off-heap memory mapped files for sharing data across processes at microsecond latency levels and high throughput.
Mutiny + quarkus
This document provides an overview of reactive programming concepts and technologies. It defines reactive programming as using asynchronous and non-blocking code to build responsive and resilient applications. It discusses reactive concepts like the event loop, back pressure, and overflow management. Frameworks like Vert.x and libraries like SmallRye Mutiny that support reactive programming on the JVM are also introduced. The key advantages of reactive programming are supporting more concurrent connections using fewer threads and efficiently processing asynchronous data streams.
High Frequency Trading and NoSQL database
This document discusses high frequency trading systems and the requirements and technologies used, including:
- HFT systems require extremely low latency databases (microseconds) and event-driven processing to minimize latency.
- OpenHFT provides low-latency logging and data storage technologies like Chronicle and HugeCollections for use in HFT systems.
- Chronicle provides microsecond-latency logging and replication between processes. HugeCollections provides high-throughput concurrent key-value storage with microsecond-level latencies.
- These technologies are useful for critical data in HFT systems where traditional databases cannot meet the latency and throughput requirements.
Background Processing - PyCon MY 2015
This document discusses using background processing to improve response times for slow webpages and views. It provides an overview of common issues like slow database writes or email sending causing timeouts. Short term solutions like "spinning" are discussed, as well as breaking tasks into preparation and processing stages to run slow tasks asynchronously. Django-background-tasks and Django-RQ are presented as options for implementing background tasks in Django, along with pros and cons. Code samples and instructions are provided for setting up and running background tasks with each.
Getting a Grip on CDN Performance - Why and How
View CDN performance data, learn how you can collect data on CDN performance and get tips on improving CDN performance.
Drilling Down Into DNS DDoS
This document discusses analyzing DNS data to detect DNS-based distributed denial-of-service (DDoS) attacks. It finds that random subdomain attacks and attacks using open home gateways and bot malware are increasingly common. These attacks strain DNS resolvers and authoritative servers by generating large volumes of recursive queries with randomized subdomains. The document recommends filtering DNS traffic at the ingress of resolvers to minimize workload and stress, while still allowing legitimate queries by using near-real-time blocklists and whitelisting valid subdomains for popular domains.
Responding rapidly when you have 100+ GB data sets in Java
One way to speed up you application is to bring more of your data into memory. But how to do you handle hundreds of GB of data in a JVM and what tools can help you.
Mentions: Speedment, Azul, Terracotta, Hazelcast and Chronicle.
Артем Оробец «На пути к low-latency»
This document discusses techniques for achieving low latency in Java applications. It begins by defining latency as the time interval between stimulation and response. For applications, total response time equals service time plus waiting time for service. Latency requirements of less than 100ms are given as an example of low latency. The document then explores specific techniques for reducing latency, such as avoiding context switching through thread pooling, optimizing logging through asynchronous approaches, addressing DNS lookup delays, and monitoring and tuning garbage collection. Overall it provides guidance on analyzing and improving various aspects of application performance to meet strict low latency goals.
Aioug connection poolsizingconcepts
The document discusses connection pool sizing concepts for web applications. It begins by describing typical web application architecture involving browsers, web servers, application servers, and database servers. It then covers topics like connection reservation, where an application thread acquires a connection from the pool to perform database work. Having too large of a connection pool can lead to database oversubscription. The document recommends sizing the connection pool based on the percentage of idle time seen in database foreground processes to avoid oversubscription. It also discusses how different software architectures, with business logic either inside or outside the database, can impact the appropriate size of the connection pool.
Perforce Server: The Next Generation
The document discusses improvements made to a database system called 100X to reduce read and write wait times. It shows that with the improvements, read wait times decreased by 17x and write wait times decreased by 1000x. The improvements involved making reads lockless so readers do not block writers. The system was also scaled out using distributed clustering across multiple nodes to improve performance and user experience.
Speed kills
Speed Kills. More accurately the lack of speed kills. It kills your visitors waiting for a page to load. It kills the search engines trying to index your site. It kills your number of page views, your rankings, your conversions, your user experience, your revenue, and the reach of your message.
This presentation is all about tips and tricks for smaller Drupal sites to speed them up like the big boys at low or no cost.
At A Small Orange we have a large number of clients who love Drupal and also love a value. We've learned a few things about site speed hosting Drupal sites on shared hosting over the years and we'd like to share that knowledge. We'll cover things like:
Out of the box cacheing
Other fun Drupal cacheing modules
3rd party services like CloudFlare
Apache stuff like Mod Deflate
DNS-OARC 34: Measuring DNS Flag Day 2020
APNIC Chief Scientist Geoff Huston presents on the change in the behaviour of DNS recursive resolvers in response to DNS Flag Day 2020.
Low latency for high throughput
Unless you have a problem which scales to many independent tasks easily e.g. web services, you may find that the best way to improve throughput is by reducing latency. This talk starts with Little's Law and it's consequences for high performance computing.
5-WebServers.ppt
This document provides an overview of internet engineering and web servers. It begins with an introduction to why companies need web services like hosting applications and websites. It then discusses the history and development of the World Wide Web and how it has grown. The document defines web servers and common features like handling HTTP requests. It covers specifics of HTTP 1.1 servers and the first web server. It also discusses the most popular web servers today like Apache and provides statistics on their usage. Finally, it provides a detailed overview of Apache web server features and functions such as caching, access control, and virtual hosting.
Semantic Web Servers
The document discusses the need for standardized protocols to enable communication between semantic web clients and servers. It proposes two such protocols: RDF Net API and Topic Map Fragment Processing. RDF Net API defines operations like query, get statements, insert statements, and remove statements. It also defines HTTP and SOAP bindings. Topic Map Fragment Processing allows clients to retrieve and update fragments of topic maps. These protocols aim to fulfill the requirements for semantic web servers to enable querying, updating, and interacting with semantic web data in a distributed environment.
More Related Content
What's hot
Fighting Spam With A Perimeter Mail System 20071108 Sasag
The document discusses moving to a tiered perimeter mail system to better fight spam. Some key points:
- Implement a tiered system with separate hardware for mail filtering services like greylisting, antivirus scanning, and spam tagging to improve scalability.
- Configure Postfix and supporting services like GLD greylisting and amavisd-new with ClamAV for antivirus to optimize performance and throughput.
- Use load testing tools like smtp-source and smtp-sink to validate the new system can handle expected mail loads before putting into production.
WordPress Powered by AMIMOTO HHVM
This document summarizes the results of performance tests between HHVM and PHP-FPM on Nginx. In a test with an increasing load from 0-300 clients over 1 minute, HHVM had a faster average response time of 1566ms compared to 3108ms for PHP-FPM. HHVM was also able to process more requests, with 386830 requests compared to 2637 for PHP-FPM. While HHVM had a slower response at higher loads, PHP-FPM became unusable and returned errors at 150-200 clients.
Cloudflare lower network latency = faster website loads
Lower network latency = faster website loads
This document discusses how lower network latency leads to faster website loads. It explains that round-trip time (RTT) measures the time for a network request to travel from one point to another and back. Faster protocols like TLS 1.3 can reduce RTT by eliminating handshake rounds. Content delivery networks (CDNs) also reduce latency by caching content closer to users worldwide. New routing technologies like Cloudflare's Argo can improve performance by up to 59% by choosing network paths based on real-time conditions instead of following indirect routes. Overall, the document emphasizes that lower latency is key to optimizing the user experience on the web.
RIPE 78: IPv6 reliability measurements
APNIC Chief Scientist Geoff Huston presents on the IPv6 reliability measurements at RIPE 78 in Reykjavík, Iceland from 20 to 24 May 2019.
Performance engineering
The document discusses various techniques for optimizing UI performance, including optimizing caching, minimizing round-trip times, minimizing request size, minimizing payload size, and optimizing browser rendering. Specific techniques mentioned include leveraging browser and proxy caching, minimizing DNS lookups and redirects, combining external JavaScript, minimizing cookie and request size, enabling gzip compression, and optimizing images. Profiling and heap analysis tools are also discussed for diagnosing backend performance issues.
Performance Tuning - Memory leaks, Thread deadlocks, JDK tools
How to identify memory leaks in java applications, thread contentions, using jdk in built tools to identify performance bottlenecks
Best Practices - PHP and the Oracle Database
Web application performance correlates with page views. Find out in this session how to maximize the performance of the OCI8 database extension to build fast, scalable web sites and attract users. Includes discussion of Oracle Database 11.2 and the upcoming PHP OCI8 1.4 extension.
Advanced off heap ipc
This document discusses advanced inter-process communication (IPC) techniques using off-heap memory in Java. It introduces OpenHFT, a company that develops low-latency software, and their open-source projects Chronicle and OpenHFT Collections that provide high-performance IPC and embedded data stores. It then discusses problems with on-heap memory and solutions using off-heap memory mapped files for sharing data across processes at microsecond latency levels and high throughput.
Mutiny + quarkus
This document provides an overview of reactive programming concepts and technologies. It defines reactive programming as using asynchronous and non-blocking code to build responsive and resilient applications. It discusses reactive concepts like the event loop, back pressure, and overflow management. Frameworks like Vert.x and libraries like SmallRye Mutiny that support reactive programming on the JVM are also introduced. The key advantages of reactive programming are supporting more concurrent connections using fewer threads and efficiently processing asynchronous data streams.
High Frequency Trading and NoSQL database
This document discusses high frequency trading systems and the requirements and technologies used, including:
- HFT systems require extremely low latency databases (microseconds) and event-driven processing to minimize latency.
- OpenHFT provides low-latency logging and data storage technologies like Chronicle and HugeCollections for use in HFT systems.
- Chronicle provides microsecond-latency logging and replication between processes. HugeCollections provides high-throughput concurrent key-value storage with microsecond-level latencies.
- These technologies are useful for critical data in HFT systems where traditional databases cannot meet the latency and throughput requirements.
Background Processing - PyCon MY 2015
This document discusses using background processing to improve response times for slow webpages and views. It provides an overview of common issues like slow database writes or email sending causing timeouts. Short term solutions like "spinning" are discussed, as well as breaking tasks into preparation and processing stages to run slow tasks asynchronously. Django-background-tasks and Django-RQ are presented as options for implementing background tasks in Django, along with pros and cons. Code samples and instructions are provided for setting up and running background tasks with each.
Getting a Grip on CDN Performance - Why and How
View CDN performance data, learn how you can collect data on CDN performance and get tips on improving CDN performance.
Drilling Down Into DNS DDoS
This document discusses analyzing DNS data to detect DNS-based distributed denial-of-service (DDoS) attacks. It finds that random subdomain attacks and attacks using open home gateways and bot malware are increasingly common. These attacks strain DNS resolvers and authoritative servers by generating large volumes of recursive queries with randomized subdomains. The document recommends filtering DNS traffic at the ingress of resolvers to minimize workload and stress, while still allowing legitimate queries by using near-real-time blocklists and whitelisting valid subdomains for popular domains.
Responding rapidly when you have 100+ GB data sets in Java
One way to speed up you application is to bring more of your data into memory. But how to do you handle hundreds of GB of data in a JVM and what tools can help you.
Mentions: Speedment, Azul, Terracotta, Hazelcast and Chronicle.
Артем Оробец «На пути к low-latency»
This document discusses techniques for achieving low latency in Java applications. It begins by defining latency as the time interval between stimulation and response. For applications, total response time equals service time plus waiting time for service. Latency requirements of less than 100ms are given as an example of low latency. The document then explores specific techniques for reducing latency, such as avoiding context switching through thread pooling, optimizing logging through asynchronous approaches, addressing DNS lookup delays, and monitoring and tuning garbage collection. Overall it provides guidance on analyzing and improving various aspects of application performance to meet strict low latency goals.
Aioug connection poolsizingconcepts
The document discusses connection pool sizing concepts for web applications. It begins by describing typical web application architecture involving browsers, web servers, application servers, and database servers. It then covers topics like connection reservation, where an application thread acquires a connection from the pool to perform database work. Having too large of a connection pool can lead to database oversubscription. The document recommends sizing the connection pool based on the percentage of idle time seen in database foreground processes to avoid oversubscription. It also discusses how different software architectures, with business logic either inside or outside the database, can impact the appropriate size of the connection pool.
Perforce Server: The Next Generation
The document discusses improvements made to a database system called 100X to reduce read and write wait times. It shows that with the improvements, read wait times decreased by 17x and write wait times decreased by 1000x. The improvements involved making reads lockless so readers do not block writers. The system was also scaled out using distributed clustering across multiple nodes to improve performance and user experience.
Speed kills
Speed Kills. More accurately the lack of speed kills. It kills your visitors waiting for a page to load. It kills the search engines trying to index your site. It kills your number of page views, your rankings, your conversions, your user experience, your revenue, and the reach of your message.
This presentation is all about tips and tricks for smaller Drupal sites to speed them up like the big boys at low or no cost.
At A Small Orange we have a large number of clients who love Drupal and also love a value. We've learned a few things about site speed hosting Drupal sites on shared hosting over the years and we'd like to share that knowledge. We'll cover things like:
Out of the box cacheing
Other fun Drupal cacheing modules
3rd party services like CloudFlare
Apache stuff like Mod Deflate
DNS-OARC 34: Measuring DNS Flag Day 2020
APNIC Chief Scientist Geoff Huston presents on the change in the behaviour of DNS recursive resolvers in response to DNS Flag Day 2020.
Low latency for high throughput
Unless you have a problem which scales to many independent tasks easily e.g. web services, you may find that the best way to improve throughput is by reducing latency. This talk starts with Little's Law and it's consequences for high performance computing.
What's hot (20)
Fighting Spam With A Perimeter Mail System 20071108 Sasag
Fighting Spam With A Perimeter Mail System 20071108 Sasag
Cloudflare lower network latency = faster website loads
Cloudflare lower network latency = faster website loads
Performance Tuning - Memory leaks, Thread deadlocks, JDK tools
Performance Tuning - Memory leaks, Thread deadlocks, JDK tools
Responding rapidly when you have 100+ GB data sets in Java
Responding rapidly when you have 100+ GB data sets in Java
Viewers also liked
5-WebServers.ppt
This document provides an overview of internet engineering and web servers. It begins with an introduction to why companies need web services like hosting applications and websites. It then discusses the history and development of the World Wide Web and how it has grown. The document defines web servers and common features like handling HTTP requests. It covers specifics of HTTP 1.1 servers and the first web server. It also discusses the most popular web servers today like Apache and provides statistics on their usage. Finally, it provides a detailed overview of Apache web server features and functions such as caching, access control, and virtual hosting.
Semantic Web Servers
The document discusses the need for standardized protocols to enable communication between semantic web clients and servers. It proposes two such protocols: RDF Net API and Topic Map Fragment Processing. RDF Net API defines operations like query, get statements, insert statements, and remove statements. It also defines HTTP and SOAP bindings. Topic Map Fragment Processing allows clients to retrieve and update fragments of topic maps. These protocols aim to fulfill the requirements for semantic web servers to enable querying, updating, and interacting with semantic web data in a distributed environment.
Web servers
This document provides an overview of web servers including:
1. It defines what a web server is and its role in serving content to web browsers over the internet.
2. It briefly summarizes the history of web servers starting with their creation by Tim Berners-Lee at CERN in the early 1990s.
3. It lists some of the most commonly used web servers today like Apache, IIS, Nginx, and GWS and provides statistics on their usage across websites globally.
Download It
This document provides an outline and overview of web servers, including Microsoft Internet Information Services (IIS) and the Apache web server. It discusses how web servers work, the architecture of web applications, and how to request documents from web servers using different programming languages like ASP.NET, PHP, and Python. It also provides instructions on setting up Apache web server with PHP enabled.
5 introduction to internet
The document provides an overview of computer and internet basics. It defines what a computer is and its basic components like hardware, software, and peripheral devices. It also explains computer functions like input, processing, storage, and output. Additionally, it describes different types of computers and networks. The document further discusses internet terminology, resources, and how to connect to and navigate the internet using browsers, email, search engines, and other applications. It provides examples and screenshots to illustrate key concepts.
Presentation (PowerPoint File)
The document provides an overview of how a web server processes an HTTP request. Key steps include:
1) Receiving the request via a listening socket and parsing it to determine the requested file.
2) Checking permissions and metadata for the file via calls like stat().
3) Opening the file, generating a response, and sending the response headers and file contents to the client socket.
4) Optimizations focus on caching frequently accessed metadata and file data in memory to avoid repeated disk operations.
Internet applications
The document discusses the World Wide Web and how to browse it using Microsoft Internet Explorer. It describes the Web as a system of interlinked hypertext documents accessed via the internet using a web browser. Users can view web pages containing text, images, videos and other media, and navigate between pages using hyperlinks. The Web was created in 1989 by Sir Tim Berners-Lee at CERN in Switzerland. The document also provides instructions on how to use a search engine like Google to find websites, and how to download files from the internet.
Servers & Web Hosting
The document discusses what a server is and the different types of servers. A server is a machine that responds to client requests across a network and provides services. There are three main types of servers - tower servers which resemble desktops and are for small organizations, rack servers which are designed to minimize space, and blade servers which are modular boards housed within a chassis. The document also covers the different roles servers can play such as file/print, application, database, email, and web servers. It then discusses web hosting options like shared hosting, dedicated servers, virtual private servers, and cloud hosting which provide varying levels of control, support, and pricing.
Web Servers - How They Work
The document discusses how web servers work and the technologies involved, including web browsers, TCP/IP, DNS, HTTP, SSL, CGI, MIME, URLs, programming languages like PHP and ASP.NET. It explains the differences between static and dynamic content, in-process and out-of-process dynamic content execution, and server-side versus client-side execution. Sample code is provided for PHP, ASP, and JavaScript to demonstrate dynamic content generation.
What Happens When You Own Google.com For A Minute?
Sanmay Ved, a former Google employee, briefly owned the domain Google.com after purchasing it through Google's domain service. He received confirmation emails intended for Google before ownership was revoked minutes later. The article speculates how someone could feel like the "master of the internet" for those few minutes and discusses possibilities for what might happen, from celebrating the purchase to concerns about how power could be misused if ownership was not revoked. It concludes by asking readers what they would do if they owned Google.com for even a brief time.
Web Server Primer
- The document discusses web servers and how they interact with browsers to deliver web pages. It compares popular web server software like Apache, IIS, and others.
- It provides guidance on selecting an appropriate web server based on factors like operating system requirements, applications needed, hardware specifications, and organizational needs.
- The document also briefly covers related servers like application servers, database servers, and proxy servers that can be used in multi-tiered architectures.
Web servers
This document discusses web servers. It provides an overview of web clients and web servers, and describes how web servers handle static and dynamic content. The document outlines the typical architecture of a two-tier or three-tier client-server system for delivering web pages. It also discusses the GET and POST request methods, phases of request handling, popular web servers like Apache and IIS, and factors to consider when selecting a web server.
Chrome OS user guide
A Chromebook is a portable computer optimized for web browsing. It runs on Chrome OS and removes complex functions to allow faster access to web-based applications and storage on the cloud. Key features include automatic updates, built-in security, and access to Google apps and documents through a web browser. The user guide provides instructions on setup, browser usage including bookmarks and printing, and changing basic configuration settings.
Web servers (l6)
Web servers handle client requests for resources on the internet by providing web pages, documents, and other files. They use the client/server model and communicate with clients using HTTP. A 3-tier architecture divides functionality into separate client, application, and database tiers. Popular web servers include Apache, Tomcat, IIS, and PWS.
Type "Google.com" into the Browser and Hit Enter: What Happens Next?
The document summarizes the steps a browser takes when a user enters "google.com" in the address bar. It checks if it is a valid URL, determines if HTTPS is preferred, checks the browser and OS caches for the domain IP address, performs a DNS lookup if needed to obtain the IP address, sets up a secure TCP connection on port 443, and sends an HTTP GET request to fetch the requested resource.
ArcReady - Scalable And Usable Web Applications
Architecting for Scalable and Usable Web Applications
As Enterprises and Software Vendors start to develop more and more applications on the Internet there is an increasing importance to architect these applications for both growth and for the optimal user experience. Software + Services allows you to develop fantastic applications, but there are pitfalls with architecting the applications in the wrong way.
Our Central Region Architect Evangelists will lead us through two great discussions on scaling web applications and creating the best possible user experience.
Session 1: Architecting for Scalable Web Applications In this session we will explore the patterns that typical applications follow as their scalability needs grow due to increased demand. We will also discuss best practices from companies that have gone up the scalability curve like Amazon.com, MySpace and Flickr. We will discuss the common bottlenecks that prevent scalability as well as how to tackle tough issues like state management in a application that is scaled across servers and even data centers. We will also discuss the “scale later” philosophy and how it should be accompanied by a solid plan to scale your applications.
Session 2: Architecting for Usable Web Applications In this session we will discuss how to architect your application with the user in mind. We have more choices than ever before for developing applications (Traditional Web Apps, AJAX, RIA technologies like Flex and Microsoft Silverlight and even smart clients) and picking the technology is only part of the solution. The architecture of the application must be designed correctly to provide a pleasing user experience and (potentially) to add new and interesting clients in the future.
Web Servers: Architecture and Security
This document summarizes the architecture and security of major web servers like IIS, Apache, and Sun JSWS. It discusses trends toward modularity, extensibility, and security. It also covers HTTP connections and keeping them alive for AJAX applications. Web servers have evolved from document retrieval to application delivery platforms.
HTTP Session Replication with Oracle Coherence, GlassFish, WebLogic
The document discusses session replication and management across WebLogic Server, GlassFish Server, and Oracle Coherence. It covers deployment models, session models, locking modes, and cluster isolation for Coherence*Web. It also provides details on integrating Coherence with WebLogic Server using ActiveCache and with GlassFish Server.
Basic computer class_3
This document provides instructions for using Internet Explorer and conducting basic internet searches. It covers opening Internet Explorer, parts of the browser like the address bar and buttons, how to navigate web pages using links and scroll bars, how to search online using search engines like Google, and safety tips for online shopping and virus protection. Students are introduced to common web sites and search engines and instructed to practice exploring sites and searching for topics that interest them.
Web Servers
The document discusses the history and features of web servers. It notes that Tim Berners-Lee created the first web server at CERN in 1989. It then discusses how web servers work and common features like modularity, virtual hosting, and authentication. The document uses Apache as a case study, noting its modular implementation, support for dynamic languages like PHP, virtual hosting, and load balancing capabilities.
Viewers also liked (20)
What Happens When You Own Google.com For A Minute?
What Happens When You Own Google.com For A Minute?
Type "Google.com" into the Browser and Hit Enter: What Happens Next?
Type "Google.com" into the Browser and Hit Enter: What Happens Next?
HTTP Session Replication with Oracle Coherence, GlassFish, WebLogic
HTTP Session Replication with Oracle Coherence, GlassFish, WebLogic
Similar to Understanding
MNPHP Scalable Architecture 101 - Feb 3 2011
An overall presentation on scaling out your system starting from a single server and many of the several options you may face.
Scalable Apache for Beginners
The document discusses performance optimization and benchmarking for Apache web servers. It covers measuring performance metrics like requests per second, latency, and scalability. Common bottlenecks like file descriptors, memory usage, and CPU overload are examined. Next generation improvements for platforms like Linux, Solaris, and 64-bit architectures that can boost Apache performance are also reviewed.
Optimizing Uptime in SOA
Initially presented at Software Architecture Conference in Boston, MA on 3/18/15.
Distributed systems are complex beasts. Breaking your application into multiple services introduces new types of errors, cascading failures, and CAP theorem limitations. Unfortunately, your uptime and sanity both suffer. This session will focus on various tactics and learnings from Lucid Software's migration to a service oriented architecture.
Introduction to performance tuning perl web applications
This document provides an introduction to performance tuning Perl web applications. It discusses identifying performance bottlenecks, benchmarking tools like ab and httperf to measure performance, profiling tools like Devel::NYTProf to find where time is spent, common causes of slowness like inefficient database queries and lack of caching, and approaches for improvement like query optimization, caching, and infrastructure changes. The key messages are that performance issues are best identified through measurement and profiling, database queries are often the main culprit, and caching can help but adds complexity.
Building a high-performance data lake analytics engine at Alibaba Cloud with ...
This document discusses optimizations made to Alibaba Cloud's Data Lake Analytics (DLA) engine, which uses Presto, to improve performance when querying data stored in Object Storage Service (OSS). The optimizations included decreasing OSS API request counts, implementing an Alluxio data cache using local disks on Presto workers, and improving disk throughput by utilizing multiple ultra disks. These changes increased cache hit ratios and query performance for workloads involving large scans of data stored in OSS. Future plans include supporting an Alluxio cluster shared by multiple users and additional caching techniques.
Clug 2011 March web server optimisation
This document discusses various techniques for optimizing website performance, including:
1. Network optimizations like compression, HTTP caching, and keeping connections alive.
2. Structuring content efficiently and using tools like YSlow to measure performance.
3. Application caching of pages, database queries, and other frequently accessed content.
4. Database tuning through indexing, query optimization, and offloading text searches.
5. Monitoring resource usage and business metrics to ensure performance meets targets.
Nephele 2.0: How to get the most out of your Nephele results
Nephele 2.0: How to get the most out of your Nephele resultsBioinformatics and Computational Biosciences Branch
The webinar covered new features and updates to the Nephele 2.0 bioinformatics analysis platform. Key updates included a new website interface, improved performance through a new infrastructure framework, the ability to resubmit jobs by ID, and interactive mapping file submission. New pipelines for 16S analysis using DADA2 and quality control preprocessing were introduced, and the existing 16S mothur pipeline was updated. The quality control pipeline provides tools to assess data quality before running microbiome analyses through FastQC, primer/adapter trimming with cutadapt, and additional quality filtering options. The webinar emphasized the importance of data quality checks and highlighted troubleshooting tips such as examining the log file for error messages when jobs fail.Webinar: Five Problems Facing Business-Critical NFS Deployments
VMware, NetApp and even EMC are proponents of using NFS based storage systems to support mission critical workloads like virtual machines, databases and performance sensitive unstructured data. But in comparison to mission critical fibre channel, the tools to monitor and optimize your NFS infrastructure are lacking. In this webinar Storage Switzerland and Virtual Instruments will discuss the five challenges facing IT professionals that depend on NFS-based storage infrastructure for performance-intensive workloads. You will learn how to detect and overcome:
* Metadata Bottlenecks
* Rogue Clients & Noisy Neighbor issues
* Server/VM Latency issues
* Poor Write Performance
* Cluster Node Bottlenecks
Handling Data in Mega Scale Systems
This document discusses strategies for handling large amounts of data in web applications. It begins by providing examples of how much data some large websites contain, ranging from terabytes to petabytes. It then covers various techniques for scaling data handling capabilities including vertical and horizontal scaling, replication, partitioning, consistency models, normalization, caching, and using different data engine types beyond relational databases. The key lessons are that data volumes continue growing rapidly, and a variety of techniques are needed to scale across servers, datacenters, and provide high performance and availability.
World Wide Web Caching
Web caching provides several benefits including bandwidth savings, reducing server load, and decreasing network latency. It works by intercepting HTTP requests and checking a local cache for the requested object before going to the origin server. Different caching approaches include proxy caching, reverse proxy caching, transparent proxy caching, and hierarchical caching. New techniques like adaptive caching and push caching aim to dynamically optimize cache placement near popular content or users.
Web Performance & Scalability Tools
This document discusses strategies for scaling web applications. It identifies key areas like the database, application, web server, scripting language, hardware, and hosting that impact scalability. Specific solutions proposed include adding servers horizontally, caching outputs, optimizing databases through indexing and load balancing, profiling applications to identify bottlenecks, tuning web and scripting language servers, using solid state drives, and leveraging the cloud for easy scaling. Resources are provided for further reading on high performance PHP and LAMP application scalability.
Del 1
This document discusses virtualization and provides guidance on virtualizing servers. It covers:
- Reasons for virtualization like increased server utilization and efficiency
- Steps for planning virtualization including addressing organizational challenges
- Factors for identifying good candidates for virtualization like application vendor support
- Best practices for the virtualization process including establishing a baseline and testing
- Potential issues to watch out for called "gotchas" and hints to improve performance
- Case studies on how Allstate and Accenture benefitted from virtualization.
Performance in business terms
You know that performance is crucial to your company's success, but do the people in the corner office know this? You need to get the message across using the language they speak and targeting the goals they care about.
This session -- presented by Strangeloop president Joshua Bixby at the 2011 Web Performance Summit -- summarizes the benefits of a faster website or web app, then delves into a series of how-tos for creating a business case for web performance in your organization.
Configuring Apache Servers for Better Web Perormance
Apache is the most popular web server in the world, yet its default configuration can't handle high traffic. Learn how to setup Apache for high performance sites and leverage many of its available modules to deliver a faster web experience for your users. Discover how Apache can max out a 1 Gbps NIC and how to serve over 140,000 pages per minute with a small Apache cluster. This presentation was given by Spark::red's founding partner Devon Hillard in March 2012 at the Boston Web Performance Meetup.
WE18_Performance_Up.ppt
The document discusses various techniques for optimizing Apache web server performance, including:
1) Monitoring tools like vmstat and top to observe server performance and detect issues.
2) Analyzing web server logs using tools like Webalizer to understand traffic patterns.
3) Configuring Apache settings like threads and processes based on the platform.
4) Caching static content and pre-rendering dynamic pages to reduce load on the server.
Digital Nightmares - The Biggest Performance Killers in Your Environment
This document provides an overview of common digital performance killers that can affect collaborative applications like Domino, Traveler and Sametime. It identifies several key areas that can degrade performance including disk I/O, memory constraints, overloaded virtual hosts, congested proxy servers, firewall and load balancer timeouts, and misconfigured LDAP servers. Specific examples are provided to illustrate how problems in these areas negatively impacted the performance of applications at various companies. The document emphasizes the importance of ongoing performance monitoring and tuning of the entire IT environment for high availability applications.
The experiences of migrating a large scale, high performance healthcare network
Lessons learned from migrating a large scale healthcare application from Windows to Unix at Partners Healthcare in Boston MA.
Black Friday and Cyber Monday- Best Practices for Your E-Commerce Database
This document provides best practices for scaling e-commerce databases for Black Friday and Cyber Monday. It discusses scaling both synchronous and asynchronous applications, efficiently using data at scale through techniques like caching, queues, and counters. It also covers scaling out through techniques like sharding, pre-sharding, and kill switches. Testing performance and capacity, as well as asking the right questions at development time are also recommended.
Some Oracle AWR observations
The document discusses various performance metrics and concepts related to database performance including database time, latency, connection pooling, resource management, and leaking issues. It provides examples of performance data and observations related to these topics. It also discusses interactions between databases and middleware and provides an example scenario, problem, analysis, and solution related to that interaction.
Gear6 Solution Launch
- The document introduces an innovative solution called centralized storage caching to close the growing performance gap between servers and disk-based storage.
- The solution involves using a scalable caching appliance to keep frequently accessed data in a large central memory pool for fast access without disk operations.
- This centralized caching approach is said to dramatically improve data throughput and access times while complementing existing storage infrastructure.
Similar to Understanding (20)
Introduction to performance tuning perl web applications
Introduction to performance tuning perl web applications
Building a high-performance data lake analytics engine at Alibaba Cloud with ...
Building a high-performance data lake analytics engine at Alibaba Cloud with ...
Nephele 2.0: How to get the most out of your Nephele results
Nephele 2.0: How to get the most out of your Nephele results
Webinar: Five Problems Facing Business-Critical NFS Deployments
Webinar: Five Problems Facing Business-Critical NFS Deployments
Configuring Apache Servers for Better Web Perormance
Configuring Apache Servers for Better Web Perormance
Digital Nightmares - The Biggest Performance Killers in Your Environment
Digital Nightmares - The Biggest Performance Killers in Your Environment
The experiences of migrating a large scale, high performance healthcare network
The experiences of migrating a large scale, high performance healthcare network
Black Friday and Cyber Monday- Best Practices for Your E-Commerce Database
Black Friday and Cyber Monday- Best Practices for Your E-Commerce Database
More from webhostingguy
File Upload
1) File uploads in PHP require configuring php.ini settings like enabling file uploads and setting temporary storage directories with correct permissions.
2) Forms for file uploads need to use POST with multipart/form-data encoding and include file input fields and hidden fields.
3) PHP stores uploaded files in the $_FILES array, including the temporary filename, size, type, and original name, which can then be processed and moved to a permanent location.
Running and Developing Tests with the Apache::Test Framework
The Apache::Test framework allows running and developing tests for Apache modules and products. Key features include:
- Running existing tests through the t/TEST program
- Setting up a new testing environment by installing Apache::Test and generating a Makefile
- Developing new tests by writing Perl scripts that use Apache::Test functions and assert results
- Options for running tests individually, repeatedly without restarts, or in parallel on different ports
MySQL and memcached Guide
This document provides instructions on installing and configuring memcached to improve the performance and scalability of MySQL. Memcached is installed using package managers or by compiling from source. It is configured to listen on ports and interfaces, allocate memory, and set thread counts. The typical usage involves applications loading data from MySQL into memcached for faster retrieval, with MySQL as the backing store if data is not found in the cache.
Novell® iChain® 2.3
The document discusses Novell iChain, a solution for securing web applications and servers. It provides single sign-on, encrypts data as it passes through proxies, and removes direct access to web servers. It authenticates users through LDAP or certificates and authorizes access through rules stored in eDirectory. This simplifies management and security across multiple web server platforms and applications.
Load-balancing web servers Load-balancing web servers
The document discusses different approaches to load balancing web servers to address issues like scaling performance, tolerating failures, and rolling upgrades. It describes three common solutions: redirecting requests through a front-end server; using round-robin DNS to distribute requests; and employing an intelligent load balancer switch that can distribute requests based on server load and detect failures. Each approach has advantages and disadvantages related to ease of implementation, visibility to users, and ability to handle session state. The document also discusses network designs and protocols involved in load balancing, including TCP connection setup and teardown.
SQL Server 2008 Consolidation
The document compares three methods for consolidating SQL Server databases: 1) multiple databases on a single SQL Server instance, 2) a single database on multiple SQL Server instances, and 3) hypervisor-based virtualization. It finds that consolidating multiple databases onto a single instance has the lowest direct costs but reduces security and manageability. Using multiple instances improves security but has higher resource needs. Hypervisor-based virtualization maintains security while enabling features like high availability, but has higher licensing costs. The document aims to help decide which approach best balances these technical and business factors for a given environment.
What is mod_perl?
Mod_perl brings together the Apache web server and Perl programming language. It allows Apache to be configured and extended using Perl, and significantly accelerates dynamic Perl content. Mod_perl supports Apache versions 1.3 and 2.x and integrates Perl at every stage of the request process to provide great flexibility and control over Apache functionality. The mod_perl community provides extensive documentation and quick support responses.
What is mod_perl?
Mod_perl brings together the Apache web server and Perl programming language. It allows Apache to be configured and extended using Perl, and significantly accelerates dynamic Perl content. Mod_perl supports Apache versions 1.3 and 2.x and integrates Perl at every stage of the request process to provide great flexibility and control over Apache functionality. The mod_perl community provides extensive documentation and quick support responses.
Notes8
The document discusses various aspects of designing an effective website, including analyzing content and target audiences, organizing site structure and navigation, and implementing design elements. The key steps outlined are to analyze content and audience needs, organize the site structure into main sections and subsections, and implement an intuitive navigation system to help users easily find relevant information. Maintaining and optimizing the site over time are also emphasized.
Dell Reference Architecture Guide Deploying Microsoft® SQL ...
This white paper provides an architectural overview and configuration guidelines for deploying Microsoft SQL Server 2005 with Microsoft Windows Server 2008 on Dell PowerEdge servers and Dell storage systems. It documents best practices for implementing SQL Server 2005 solutions using Dell hardware and software components that have been tested and validated to help ensure successful deployment and optimal performance. The white paper covers storage configuration, network configuration, operating system configuration, and SQL Server configuration recommendations.
Managing Diverse IT Infrastructure
1. The document discusses the evolution of business models for IT infrastructure from proprietary systems within individual companies to more open standards and shared infrastructure leveraging the internet.
2. It describes new service models like client-server computing, web services, and on-demand/utility computing which allow flexible provisioning of computing resources on a needs basis.
3. Managing diverse IT infrastructures requires considerations around outsourcing non-core functions, developing service level agreements, managing legacy systems, and aligning infrastructure capabilities to business strategy through appropriate investment.
Web design for business.ppt
The document discusses different types of websites that can be created for business purposes including traditional, blog-based, and group/network sites. It provides information on setting up each type of site for free or at low cost using online tools or designers, and how to add features like domains, payment systems, and linking domains to sites. Options for free and cheap site creation using tools like Google Sites are demonstrated.
IT Power Management Strategy
This document outlines Saint Louis University's strategy for improving power management of IT equipment to reduce costs and environmental impact. Key points include:
1) SLU aims to standardize power-optimized default settings on all managed PCs and laptops through automated software and establish policies around exceptions and existing devices.
2) Potential savings are estimated from generational improvements in computer hardware and adopting lower-power modes like sleep versus screensavers.
3) The strategy also involves consolidating servers, enabling energy-efficient settings on printers and other electronics, and establishing institutional goals around student computer energy use.
Excel and SQL Quick Tricks for Merchandisers
This document provides instructions for using Microsoft SQL and Excel to extract data from a SmartSite SQL database, manipulate it in Excel using functions, and update the SQL tables with the modified data to streamline content work. It covers connecting to and querying SQL databases, common Excel functions for editing data, and steps for importing an Excel file into a SQL table to update information. Examples of specific SQL queries and Excel functions are provided along with a scenario walking through the full process.
OLUG_xen.ppt
The document discusses various topics related to virtualization including drivers for virtualization, practical applications, definitions of terms like virtualization and paravirtualization, and tools like Xen, VMWare, and Microsoft virtualization products. It provides information on installing and configuring Xen on SuSE Linux, discusses security and auditing considerations for Xen, and demonstrates Xen functionality.
Parallels Hosting Products
The document discusses strategies for converting low-value hosting clients into high-value customers by marketing additional services. It recommends continuously marketing to clients through email, forums, blogs and surveys to promote add-on services like collaboration tools, applications, and infrastructure-as-a-service offerings which can significantly increase revenue per client. Measuring marketing campaigns and conversions is key to optimizing efforts to up-sell existing clients.
Microsoft PowerPoint presentation 2.175 Mb
The document discusses WebMapping Solutions and their products and services. It summarizes their middleware and mapping tools like MapBroker, Generic GUI Builder, and MapOrganiser. MapBroker powers many of their applications. Their products allow users to build custom web mapping applications and manage both geographic and non-geographic data in a single view. Their services include publishing data online, application development, and strategic consulting. Some examples of government and organization clients are listed.
Reseller's Guide
This document provides an overview and guide for using HSPcomplete, a hosting automation solution that allows hosting service providers to manage infrastructure, billing, sales channels, and e-commerce through a single system. It describes HSPcomplete's advantages like integrated billing and credit card processing, virtual private server management, and domain registration. Hardware, software, and user requirements for HSPcomplete deployment are also outlined.
More from webhostingguy (20)
Running and Developing Tests with the Apache::Test Framework
Running and Developing Tests with the Apache::Test Framework
Load-balancing web servers Load-balancing web servers
Load-balancing web servers Load-balancing web servers
PHP and MySQL PHP Written as a set of CGI binaries in C in ...
PHP and MySQL PHP Written as a set of CGI binaries in C in ...
Dell Reference Architecture Guide Deploying Microsoft® SQL ...
Dell Reference Architecture Guide Deploying Microsoft® SQL ...
Understanding
- 1. Understanding & Addressing Blocking-Induced Server Latency Yaoping Ruan IBM T.J. Watson Research Center Vivek Pai Princeton University
- 11. Response Time vs Dataset Size >99.5 % cache hits
- 13. Ideal Service Breakdown small files large files
- 14. Flash Service Breakdown Flash CDF breakdown by decile at load level 0.95 Service inversion at this level is 0.58 small files large files
- 15. Apache Service Breakdown Apache CDF breakdown by decile at load level 0.95 Service inversion at this level is 0.58 small files large files
- 22. Response Time vs. Dataset
- 23. Flash Service Breakdowns Flash New-Flash
- 24. Flashpache Service Breakdowns Apache Flashpache
- 25. Latency Scalability Response time at 0.95 load level
- 28. Thank you www.cs.princeton.edu/nsg/papers Princeton University Network Systems Group
- 29. Apache on Linux Apache Flashpache
- 30. Effects on Response Time Flash latency CDFs
Editor's Notes
- Response time: sending last byte of request, receiving last byte of response Why last byte of response, server drop connections