1 Part VII Component-level Performance Models for the Web © 1998 Menascé & Almeida. All Rights Reserved.

Slides:



Advertisements
Similar presentations
1 Evaluation of applications over an intranet. 2 FDDI 100 Mbps Lan 5 R1 R3 R2 R4 Lan 1 10 Mbps Eth Lan 2 10 Mbps Eth Lan 3 10 Mbps Eth Lan 4 16 Mbps TR.
Advertisements

Adapted from Menascé & Almeida.1 Workload Characterization for the Web.
Ó 1998 Menascé & Almeida. All Rights Reserved.1 Part IV Capacity Planning Methodology.
Performance Engineering Methodology Chapter 4. Performance Engineering Performance engineering analyzes the expected performance characteristics of a.
Adapted from Menascé & Almeida1 Web and Intranet Performance Issues.
1 Part IV Capacity Planning Methodology © 1998 Menascé & Almeida. All Rights Reserved.
1Adapted from Menascé & Almeida. Capacity Planning Methodology.
July 2003SPECTS Network-Level Impacts on User-Level Web Performance Carey Williamson Nayden Markatchev University of Calgary.
EEC-484/584 Computer Networks Lecture 6 Wenbing Zhao
1 Part II Web Performance Modeling: basic concepts © 1998 Menascé & Almeida. All Rights Reserved.
Application Layer  We will learn about protocols by examining popular application-level protocols  HTTP  FTP  SMTP / POP3 / IMAP  Focus on client-server.
CSE 190: Internet E-Commerce Lecture 16: Performance.
EEC-484/584 Computer Networks Discussion Session for HTTP and DNS Wenbing Zhao
1 Part III Web and Intranet Performance Issues © 1998 Menascé & Almeida. All Rights Reserved.
1 Web Performance Modeling Chapter New Phenomena in the Internet and WWW Self-similarity - a self-similar process looks bursty across several time.
Single queue modeling. Basic definitions for performance predictions The performance of a system that gives services could be seen from two different.
1 Multiple class queueing networks Mean Value Analysis - Open queueing networks - Closed queueing networks.
1Adapted from Menascé & Almeida. Capacity Planning Methodology.
1 Internet Management and Security We will look at management and security of networks and systems. Systems: The end nodes of the Internet Network: The.
Capacity planning for web sites. Promoting a web site Thoughts on increasing web site traffic but… Two possible scenarios…
1 Part VI System-level Performance Models for the Web © 1998 Menascé & Almeida. All Rights Reserved.
Application Layer  We will learn about protocols by examining popular application-level protocols  HTTP  FTP  SMTP / POP3 / IMAP  Focus on client-server.
Proxy servers By Akshit, Jay and Bhum Y10. What is a proxy server O A proxy server is a computer that offers a computer network service to allow clients.
COMPUTER TERMS PART 1. COOKIE A cookie is a small amount of data generated by a website and saved by your web browser. Its purpose is to remember information.
Proxy servers By Akshit Y10. What is a proxy server O A proxy server is a computer that offers a computer network service to allow clients to make indirect.
CLIENT A client is an application or system that accesses a service made available by a server. applicationserver.
Computer System Lifecycle Chapter 1. Introduction Computer System users, administrators, and designers are all interested in performance evaluation. Whether.
Ekrem Kocaguneli 11/29/2010. Introduction CLISSPE and its background Application to be Modeled Steps of the Model Assessment of Performance Interpretation.
Computer Networks Performance Evaluation
Performance of Web Applications Introduction One of the success-critical quality characteristics of Web applications is system performance. What.
Ó 1998 Menascé & Almeida. All Rights Reserved.1 Part III Web and Intranet Performance Issues.
M EAN -V ALUE A NALYSIS Manijeh Keshtgary O VERVIEW Analysis of Open Queueing Networks Mean-Value Analysis 2.
5 Chapter Five Web Servers. 5 Chapter Objectives Learn about the Microsoft Personal Web Server Software Learn how to improve Web site performance Learn.
Ó 1998 Menascé & Almeida. All Rights Reserved.1 Part III Web and Intranet Performance Issues (Book, chap. 4)
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Identifying Application Impacts on Network Design Designing and Supporting Computer.
Protocol(TCP/IP, HTTP) 송준화 조경민 2001/03/13. Network Computing Lab.2 Layering of TCP/IP-based protocols.
E-Commerce Architectures and Technologies Rob Oshana Southern Methodist University.
Computer Networks Performance Metrics. Performance Metrics Outline Generic Performance Metrics Network performance Measures Components of Hop and End-to-End.
Lect3..ppt - 09/13/04 CIS 4100 Systems Performance and Evaluation Lecture 4 by Zornitza Genova Prodanoff.
A Measurement Based Memory Performance Evaluation of High Throughput Servers Garba Isa Yau Department of Computer Engineering King Fahd University of Petroleum.
Understanding the Performance of Web Caching System with an Analysis Model and Simulation Xiaosong Hu Nur Zincir-Heywood Sep
1 PREFETCHING INLINES TO IMPROVE WEB SERVER LATENCY Ronald Dodge US Army Daniel Menascé, Ph. D. George Mason University
© 1995 Daniel A. Menascé Capacity Planning in Client/Server Environments Daniel A. Menascé George Mason University Fairfax, VA 22030
1 Challenges in Scaling E-Business Sites  Menascé and Almeida. All Rights Reserved. Daniel A. Menascé Department of Computer Science George Mason.
Data Communications and Computer Networks Chapter 2 CS 3830 Lecture 8 Omar Meqdadi Department of Computer Science and Software Engineering University of.
yahoo.com SUT-System Level Performance Models yahoo.com SUT-System Level Performance Models8-1 chapter11 Single Queue Systems.
Queueing Models with Multiple Classes CSCI 8710 Tuesday, November 28th Kraemer.
Ó 1998 Menascé & Almeida. All Rights Reserved.1 Part VIII Concluding Remarks.
Performance of Web Proxy Caching in Heterogeneous Bandwidth Environments IEEE Infocom, 1999 Anja Feldmann et.al. AT&T Research Lab 발표자 : 임 민 열, DB lab,
Ó 1998 Menascé & Almeida. All Rights Reserved.1 Part V Workload Characterization for the Web.
1 Components performance modelling - Outline of queue networks - Mean Value Analisys (MVA) for open and close queue networks.
Measuring the Capacity of a Web Server USENIX Sympo. on Internet Tech. and Sys. ‘ Koo-Min Ahn.
Ó 1998 Menascé & Almeida. All Rights Reserved.1 Part VI System-level Performance Models for the Web (Book, Chapter 8)
Internet Applications: Performance Metrics and performance-related concepts E0397 – Lecture 2 10/8/2010.
MiddleMan: A Video Caching Proxy Server NOSSDAV 2000 Brian Smith Department of Computer Science Cornell University Ithaca, NY Soam Acharya Inktomi Corporation.
Ó 1998 Menascé & Almeida. All Rights Reserved.1 Part II System Performance Modeling: basic concepts, operational analysis (book, chap. 3)
Introduction to Networking
1 COMP 431 Internet Services & Protocols HTTP Persistence & Web Caching Jasleen Kaur February 11, 2016.
09/13/04 CDA 6506 Network Architecture and Client/Server Computing Peer-to-Peer Computing and Content Distribution Networks by Zornitza Genova Prodanoff.
تجارت الکترونیک سیار جلسه هفتم مدرس : دکتررامین کریمی.
Ó 1998 Menascé & Almeida. All Rights Reserved.1 Part VIII Web Performance Modeling (Book, Chapter 10)
تجارت الکترونیک سیار جلسه پنجم مدرس : دکتررامین کریمی.
Network Processing Systems Design
Ó 1998 Menascé & Almeida. All Rights Reserved.1 Part VI System-level Performance Models for the Web.
Lecture 2: Performance Evaluation
Application Software Platform Services Graphics Data Interchange
Department of Computer Science University of Calgary
Technologies and Applications
Queuing Theory Queuing Theory.
Queuing Analysis.
Presentation transcript:

1 Part VII Component-level Performance Models for the Web © 1998 Menascé & Almeida. All Rights Reserved.

2 Part VII: Learning Objectives Characterize component-level models Compute demands on system resources. Compute waiting times, response times, throughputs. –open models (e.g., web servers) –closed models (e.g., intranets)

3 Component-level Models The internal components of a server (e.g., processors, disks) as well as network links are modeled explicitly. Changes in server architecture, component upgrades (e.g., use of a faster CPU or faster network connections) can be evaluated with component-level models.

4 Component-level models server incoming link outgoing link server

5 Component-level models server cpu disk 1 disk 2 incoming link outgoing link server

6 Component-level models server cpu disk 1 disk 2 incoming link outgoing link server

7 Component-level Models Each component is represented by a resource (e.g. CPU, disk, communication link) and a queue of requests waiting for the resource. resource queue

8 Component-level Models Parameters Service demand of a request at a resource: total service time of the request at the device. cpu D cpu = total CPU time of a request

9 Computing Service Demands cpu disk 1 disk 2 incoming link outgoing link server The average size of a file retrieved per request is 20KBytes. The average disk service time per KByte accessed is 10msec. 40% of the files are on disk 1 and 60% on disk 2. The speed of the link connecting the server to the Internet is 1.5 Mbps (a T1 link). The CPU processing time per request is 2 msec msec per KByte accessed. The average size of an HTTP request is 200 bytes.

10 Disk Service Demand cpu disk 1 disk 2 incoming link outgoing link server The average size of a file retrieved per request is 20KBytes. The average disk service time per KByte accessed is 10 msec. 40% of the files are on disk 1 and 60% on disk 2. D disk1 = 0.4*10 msec/Kbyte * 20KBytes = 80 msec = sec D disk2 = 0.6*10 msec/Kbyte * 20KBytes = 120 msec = sec

11 CPU Service Demand cpu disk 1 disk 2 incoming link outgoing link server The average size of a file retrieved per request is 20KBytes. The CPU processing time per request is 2 msec msec per KByte accessed. D cpu = 2 msec msec/KByte * 20 Kbyte = 3 msec = sec

12 Incoming Link Service Demand The speed of the link connecting the server to the Internet is 1.5 Mbps (a T1 link). The average size of an HTTP request is 200 bytes. D IncLink = 200 * 8 bits / 1,500,000 bps = sec cpu disk 1 disk 2 incoming link outgoing link server

13 Outgoing Link Service Demand cpu disk 1 disk 2 incoming link outgoing link server The average size of a file retrieved per request is 20KBytes. The speed of the link connecting the server to the Internet is 1.5 Mbps (a T1 link). D OutLink = 20 * 1024 * 8 bits / 1,500,000 bps = sec

14 Computing Service Demands cpu disk 1 disk 2 incoming link outgoing link server sec sec sec 0.08 sec 0.12 sec Service demands do not include any queuing time! It is just service time.

15 Your company decided to add multimedia content to the Web-based training application. The average size of a Web document will increase from 10 Kbytes to 80Kbytes. Assuming the same disk will be used, what changes need to be made to the model to predict the performance in this new scenario? Practice Drill Practice Drill Using Models for Decision Making

16 The web-based human resources application is being rewritten. CGI scripts will be replaced by Java applets. Early prototyping showed that the Java -based solution uses 80% less CPU than its CGI-based counterpart. How should the model be changed to reflect the new software architecture? Practice Drill Practice Drill Using Models for Decision Making

17 Computing Waiting Times Waiting times depend on the load (arrival rate of requests) and on the service demands. cpu disk 1 disk 2 incoming link outgoing link server sec sec sec 0.08 sec 0.12 sec

18 Computing Residence Times n transactions seen, on the avg, by arriving request J. Each of the n requests found by J need D sec of total service. So, J has to wait for n * D seconds before being served. If we add J’s total service time D we get J’s residence time R at the resource: D J n R R = D + n*D From Little’s Law: n = R * So, R = D + R * * D R = D / (1 - * D )

19 Computing Residence Times DiDi RiRi Service demand at resource i Utilization of resource i (U i )

20 Residence Time at Incoming Link cpu disk 1 disk 2 incoming link outgoing link Web server sec sec sec 0.08 sec 0.12 sec  req/sec

21 Residence Time at Outgoing Link cpu disk 1 disk 2 incoming link outgoing link Web server sec sec sec 0.08 sec 0.12 sec  req/sec

22 Residence Time at the CPU cpu disk 1 disk 2 incoming link outgoing link Web server sec sec sec 0.08 sec 0.12 sec  req/sec

23 Residence Time at Disk 1 cpu disk 1 disk 2 incoming link outgoing link Web server sec sec sec 0.08 sec 0.12 sec  req/sec

24 Residence Time at Disk 2 cpu disk 1 disk 2 incoming link outgoing link Web server sec sec sec 0.08 sec 0.12 sec  req/sec

25 Summary of Results Average Response Time

26 Response vs. Arrival Rate

27 Your company’s Web site is becoming popular. It is expected that the load will double in the next two months from its current load of 6 HTTP requests/sec. Management is considering installing an additional T1 link. Before making the investment, the company wants to know what is the performance gain? Practice Drill Practice Drill Using Models for Decision Making

28 Which model parameters need to be changed? Practice Drill Practice Drill Using Models for Decision Making

29 Open vs. Closed QN Models The models presented so far are open QN models because there is no limit on the number of requests in the system. When the number of requests in the system is limited, we need closed QN models. –e.g., servers with limited degree of MPL. –C/S systems with known number of clients.

30 Open Model Equations

31 Multiple Classes of Requests Different HTTP requests may have different file sizes, frequency of arrival and different resource service demands.

32 Equations for Open Multiple Class QN Models

33 Multiclass Example A Web server has one CPU and two disks. It receives two types of HTTP requests: for small text files and for large images. The average arrival rates are 5 requests/sec for text and 2 requests/sec for images. What is the response times for each type of request?

34

35

36

37 A Complete Web Server Example Web server 10 Mbps Ethernet router (50  sec/packet) T1 link ISPInternet 6 HTTP req/sec

38 A Complete Web Server Example (cont’d) incoming link outgoing link routerLAN cpu disk Web server

39 A Complete Web Server Example (cont’d) Workload

40 A Web Server Example (cont’d)

41 A Web Server Example (cont’d)

42 A Web Server Example (cont’d)

43 A Web Server Example (cont’d)

44 A Web Server Example (cont’d)

45 major contribution to service demand A Web Server Example (cont’d)

46 Closed QN Model A Web server has one CPU and one disk. Assume that n requests are in execution concurrently. Each request takes 3 msec of CPU and 10 msec of disk time. What is the throughput and response time of the Web server?

47 Closed QN Model cpu disk Web server n

48 Closed QN Model Residence Time Equations: my service time avg. number of requests in the CPU found upon my arrival my total waiting time at the CPU

49 Closed QN Model Residence Time Equations:

50 Closed QN Model Throughput Equation. Using Little’s Law: total response time throughput

51 Closed QN Model Throughput Equation:

52 Closed QN Model Queue Length Equations. Applying Little’s Law and the Forced Flow Law to the CPU and disk.

53 Putting It All Together

54 Putting It All Together

55 Putting It All Together

56 Solving the Model

57 Solving the Model

58 Solution to the Closed QN model

59 Solution to the Closed QN model

60 Closed Models Equations

61 An Intranet Example with Proxy Cache Server Clients Proxy Server External Web Servers router (50  sec/packet) Internet LAN (10 Mbps Ethernet)......

62 An Intranet Example (cont’d) Cache Hit routerLAN cpu disk proxy cache server incoming link outgoing link ISP Internet web server clients

63 An Intranet Example (cont’d) Cache Miss routerLAN cpu disk proxy cache server incoming link outgoing link ISP Internet web server clients

64

65 largest service demand throughput in HTTP req/sec

66

67 Intranet Example Increasing the Bandwidth of the link to the ISP

68 Part VII: Summary Component-level models are used to represent the various components of a networked system. Parameters for component-level models include the service demands on system resources, i.e. total time spent by a request receiving service from a resource.

69 Part VII: Summary (cont’d) Waiting times, response times, throughputs can be computed using –open models (e.g., web servers) –closed models (e.g., intranets)