Commit 66ce841e authored by Robert Ricci's avatar Robert Ricci

Clear out old notes

parent c7f21f4d
\setmainfont[Numbers=OldStyle,Ligatures=TeX]{Equity Text A}
\newfontfamily\titlefont[Numbers=OldStyle,Ligatures=TeX]{Equity Caps A}
\title{CS6963 Lecture \#13}
\title{CS6963 Lecture \#15}
\author{Robert Ricci}
\date{February 27, 2014}
\date{March 10, 2015}
......@@ -21,55 +14,6 @@
\1 What we decided last time:
\2 Remember, overall goal is to decide whether to use NewReno or cubic TCP on
our webserver, and whether or not to enable SACK
\2 SUT includes network and NIC, but not webserver or client
\2 Questions to answer:
\3 Which variant provides higher througput / goodput?
\3 Which variant gives lower delay?
\3 Which provides better fairness between clients?
\3 How many TCP sessions / clients can we support?
\2 Secondary things to look at:
\3 How many retransmissions are caused?
\3 What is the utilization on the server NIC?
\3 What is the interaction between the application and TCP?
\1 Things to decide for today:
\2 What metrics will we use?
\2 What are the parameters?
\2 Which ones will will vary as factors?
\3 How will we decide what values they should take on?
\2 What will we use as our workload generator?
\2 How will we collect measurements?
\2 What will our major set of evaluations be?
\2 How will we present results?
\item[Client workload generator: Naveen, Binh] \hfill \\
A tool for actually making http requests; we should be reasonably confident that this tool does not itself cause some kind of bottleneck or timing artifacts, which would make it part of the system under test, which we decided we didn't want it to be. This tool is going to need to be capable of, or scriptable to, make requests to URLs according to some distribution and with some timing models (eg. how long do I wait between page loads, do I wait for the previous page load to load the next page, etc.)
\item[Server to respond to clients: Christopher, Hyunwook] \hfill \\
Like the client, we need to be confident that the server introduces minimal effects on the system so that it does not become part of the system under test. We need to be able to serve objects of varying size according to some distribution.
\item[Tools for analyzing client to server communication: Ren, Philip] \hfill \\
We decided that we would capture the response variables (bandwidth, latency, etc.) at the layer of capturing packets on the wire. So, we will need to decide what tools to use to capture these packets, and we will need to be able to compute these higher-level metrics from the raw traces that we collect.
\item[Data about distribution of web requests: Chaitu, Aisha] \hfill \\
We need to cause the client program to make requests according to some distribution of requests that is representative of that seen by real webservers - for example, what are the sizes of objects fetched, what is the time between objects being fetched, what is the ratio of data downloaded from the server vs. data uploaded to the server. As much as possible, we should use distributions gathered from real systems, so we should try to find studies, traces, datasets, etc.
\item[Data about distribution of client network performance: Junguk, Makito] \hfill \\
We need to model some network conditions between the clients and the server: what is their roundtrip latency to the server, what bandwidth do they have available, what packet loss rates do they see, etc. As with the distribution of requests, we should try to use distributions gathered from real networks, and should look for studies, etc. giving us distributions to use for these values
\1 For next time
\2 Read Chapter 14, linear regression
......@@ -77,6 +21,4 @@
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment