DotSlash: Providing Dynamic Scalability to Web Applications Weibin Zhao and Henning Schulzrinne Department of Computer Science, Columbia University More.

Slides:



Advertisements
Similar presentations
Internet Applications INTERNET APPLICATIONS. Internet Applications Domain Name Service Proxy Service Mail Service Web Service.
Advertisements

Performance Testing - Kanwalpreet Singh.
Welcome to Middleware Joseph Amrithraj
The architecture diagram of our IPv6 content addressing system. In our system, the regular browser makes a HTTP request through a proxy, which translates.
High Performance Computing Course Notes Grid Computing.
Prime’ Senior Project. Presentation Outline What is Our Project? Problem Definition What does our system do? How does the system work? Implementation.
1 Content Delivery Networks iBAND2 May 24, 1999 Dave Farber CTO Sandpiper Networks, Inc.
Module 8: Concepts of a Network Load Balancing Cluster
Chapter 8: Web Server Hardware and Software. Electronic Commerce, Seventh Annual Edition2 Web Server Basics The main job of a Web server computer is to.
DotSlash – A Web Hotspot Rescue System Weibin Zhao Henning Schulzrinne Department of Computer Science Columbia University June 11, 2004.
Web Caching Schemes1 A Survey of Web Caching Schemes for the Internet Jia Wang.
Web Server Hardware and Software
CSE 190: Internet E-Commerce Lecture 16: Performance.
Web Servers How do our requests for resources on the Internet get handled? Can they be located anywhere? Global?
Handling Web Hotspots at Dynamic Content Web Sites Using DotSlash Weibin Zhao Henning Schulzrinne Columbia University NYMAN’04.
Handling Web Hotspots at Dynamic Content Web Sites Using DotSlash Weibin Zhao Henning Schulzrinne Columbia University Dagstuhl.
Adaptive Content Delivery for Scalable Web Servers Authors: Rahul Pradhan and Mark Claypool Presented by: David Finkel Computer Science Department Worcester.
Nikolay Tomitov Technical Trainer SoftAcad.bg.  What are Amazon Web services (AWS) ?  What’s cool when developing with AWS ?  Architecture of AWS 
Weibin Zhao Henning Schulzrinne Department of Computer Science Columbia University.
Capacity planning for web sites. Promoting a web site Thoughts on increasing web site traffic but… Two possible scenarios…
Internet Real Time (IRT) Lab at Columbia University Professor: Henning Schulzrinne Columbia University Presenter: Suman Srinivasan, PhD student
Towards Autonomic Computing: Service Discovery and Web Hotspot Rescue Weibin Zhao Department of Computer Science Columbia University.
March 31, 2005Thomson1 Advanced Network Services: P2P VoIP, location-based services and self-managing server farms Henning Schulzrinne (and members of.
Windows Server 2008 Chapter 8 Last Update
Hands-On Microsoft Windows Server 2008 Chapter 8 Managing Windows Server 2008 Network Services.
Computer Science Cataclysm: Policing Extreme Overloads in Internet Applications Bhuvan Urgaonkar and Prashant Shenoy University of Massachusetts.
10/02/2004ELFms meeting1 Linux Virtual Server Miroslav Siket FIO-FS.
1 Content Distribution Networks. 2 Replication Issues Request distribution: how to transparently distribute requests for content among replication servers.
Active Network Applications Tom Anderson University of Washington.
{ Content Distribution Networks ECE544 Dhananjay Makwana Principal Software Engineer, Semandex Networks 5/2/14ECE544.
Krerk Piromsopa. Advance Net-Centric Computing Technology Krerk Piromsopa. Department of Computer Engineering. Chulalongkorn University.
Advanced Network Architecture Research Group 2001/11/149 th International Conference on Network Protocols Scalable Socket Buffer Tuning for High-Performance.
Performance of Web Applications Introduction One of the success-critical quality characteristics of Web applications is system performance. What.
Lectures and Practicals Mon 8-10 SC1222 TUE SC1222 Office: SC Website: mis.csit.sci.tsu.ac.th/kanida.
CINEMA’s UbiComp Subsystem Stefan Berger and Henning Schulzrinne Department of Computer Science Columbia University
Database Replication Policies for Dynamic Content Applications Gokul Soundararajan, Cristiana Amza, Ashvin Goel University of Toronto EuroSys 2006: Leuven,
Infrastructure for Better Quality Internet Access & Web Publishing without Increasing Bandwidth Prof. Chi Chi Hung School of Computing, National University.
DotSlash An Automated Web Hotspot Rescue System Jonathan Bulava CSC8530 – Distributed Systems Dr. Paul Schragger.
2: Application Layer1 Chapter 2 outline r 2.1 Principles of app layer protocols r 2.2 Web and HTTP r 2.3 FTP r 2.4 Electronic Mail r 2.5 DNS r 2.6 Socket.
SPrint: A Smart Printing Service for Siebel Center Imranul Hoque, Sonia Jahid, Ahsan Arefin {ihoque2, sjahid2, illinois.edu Department of Computer.
Bellwether: Surrogate Services for Popular Content Duane Wessels & Ted Hardie NANOG 19 June 12, 2000.
Peer-to-peer systems for autonomic VoIP and web hotspot handling Kundan Singh, Weibin Zhao and Henning Schulzrinne Internet Real Time Laboratory Computer.
Module 11: Implementing ISA Server 2004 Enterprise Edition.
1 Specification and Implementation of Dynamic Web Site Benchmarks Sameh Elnikety Department of Computer Science Rice University.
Applications Web et bases de données en grappe Séminaire InTech 3 Février 2005 – Grenoble.
DotSlash: Handling Web Hotspots at Dynamic Content Web Sites Weibin Zhao Henning Schulzrinne Department of Computer Science Columbia.
Server Performance, Scaling, Reliability and Configuration Norman White.
Web Architecture Introduction
(c) Lindsay Bradford1 Varying Resource Consumption to achieve Scalable Web Services Lindsay Bradford Centre for Information Technology Innovation.
Empirical Quantification of Opportunities for Content Adaptation in Web Servers Michael Gopshtein and Dror Feitelson School of Engineering and Computer.
Setup and Management for the CacheRaQ. Confidential, Page 2 Cache Installation Outline – Setup & Wizard – Cache Configurations –ICP.
DotSlash – or how to deal with 15 minutes of fame Weibin Zhao Henning Schulzrinne Columbia University CATT/WICAT Annual Research Review November 14, 2003.
Globally Distributed Content Delivery Presenter: Baoning Wu 03/25/2003.
Web Server Apache PHP HTTP Request User types URL into browser Address resolved if nec. We use directly Most browsers request.
BZUPAGES.COM WEB SERVER PRESENTED TO: SIR AHMAD KAREEM.
09/13/04 CDA 6506 Network Architecture and Client/Server Computing Peer-to-Peer Computing and Content Distribution Networks by Zornitza Genova Prodanoff.
Basics of the Domain Name System (DNS) By : AMMY- DRISS Mohamed Amine KADDARI Zakaria MAHMOUDI Soufiane Oujda Med I University National College of Applied.
Web Cache. What is Cache? Cache is the storing of data temporarily to improve performance. Cache exist in a variety of areas such as your CPU, Hard Disk.
Cofax Scalability Document Version Scaling Cofax in General The scalability of Cofax is directly related to the system software, hardware and network.
Fault – Tolerant Distributed Multimedia Streaming Web Application By Nirvan Sagar – Srishti Ganjoo – Syed Shahbaaz Safir
Presented by Michael Rainey South Mississippi Linux Users Group
Scaling Network Load Balancing Clusters
Coral: A Peer-to-peer Content Distribution Network
CIIT-Human Computer Interaction-CSC456-Fall-2015-Mr
Network Load Balancing
PHP / MySQL Introduction
DotSlash: An Automated Web Hotspot Rescue System
AWS Cloud Computing Masaki.
Co-operative Server Pool for Hotspot Rescue Service
Web Servers (IIS and Apache)
Presentation transcript:

DotSlash: Providing Dynamic Scalability to Web Applications Weibin Zhao and Henning Schulzrinne Department of Computer Science, Columbia University More information available from or by to The Problem Web hotspots, also known as flash crowds, or the Slashdot effect Short-term dramatic load spikes  “15 minutes of fame” Unacceptable to sacrifice availability by losing valuable users in the critical period, but uneconomic to invest on more powerful infrastructure which is idle most of time DotSlash Approach A self-configuring and scalable rescue system designed to counteract the Slashdot effect, which allows a web site to obtain resources dynamically and use them autonomically without any administrative intervention to set up a distributed web server system on the fly Providing dynamic scalability to web applications by addressing bottlenecks at access network bandwidth, web servers, application servers, and database servers Usage Models Focusing on small web sites Aiming at utilizing spare capacity in a mutual-aid community to handle short-term load spikes, also useful for commercial hosting companies Advantages Transparent to clients and applications: no need to change client browsers and application programs Low cost: based on existing systems, no additional hardware cost Basic Components Workload monitoring for network and CPU Rescue server discovery Request redirection via DNS round robin and HTTP redirect Dynamic virtual hosting for serving new content on the fly Adaptive rescue control Dynamic replication of application programs On-demand distributed query result caching DotSlash Implementation A prototype system for the LAMP (Linux, Apache, MySQL, and PHP) configuration A DotSlash Apache module (Mod_dots) for per request processing A DotSlash daemon (Dotsd) for rescue control A DotSlash PHP extension for dynamic script replication A cache-enhanced PHP data driver for MySQL databases for on-demand query result caching DNS domain dot-slash.net for dynamic DNS update Enhanced Service Location Protocol (SLP) for rescue server discovery BINDmSLP HTTP Shared Memory SLP DNS DotSlash Other Dotsd Apache Dotsd Mod_dots DotSlash Performance Benchmarks: httperf for static content and RUBBoS bulletin board for dynamic content Experimental setup: our local area network and PlanetLab Achieve a 10-fold improvement for static content when access network is bottleneck Completely remove the web/application server bottleneck via dynamic script replication Relieve the database server bottleneck via on- demand query result caching Improve the maximum request rate supported by a factor of 5 and 10 for the RUBBoS submission and read-only mix, respectively Basic Rescue origin.com rescue.com Client (1) (2) (3)(4) HTTP redirect alias1.rescue.com (8) Reverse proxy (5) alias1.rescue.com (6) (9) (10)(7) Dynamic DNS DNS RR origin.com DNS rescue.com DNS Cache Client2 (2) (1) (4) (3) I. HTTP redirect & cache miss II. DNS RR & cache hit Basic Architecture MySQL Apache (5) PHP(6) (1) (2) (3) Dynamic Script Replication (4) (7) Origin Server Rescue Server Client Database Server (8) Apache On-demand Query Result Caching Web/Application Server Query Result Cache Data Driver Client Database Server Database Server Web/Application Server Query Result Cache Data Driver Rescue Server Origin Server Client Rescue Protocol