Update to Tracing Paper

	- Additions to results and assumption sections

TracingPaper.aux

@@ -81,17 +81,17 @@
 \citation{RuemmlerWilkes1993}
 \citation{Bolosky2007}
 \citation{EllardLedlie2003}
-\bibcite{Leung2008}{1}
-\bibcite{Ellard2003}{2}
-\bibcite{EllardLedlie2003}{3}
 \@writefile{toc}{\contentsline {subsection}{\numberline {3.3}Locating Performance Bottlenecks}{6}}
 \newlabel{Locating Performance Bottlenecks}{{3.3}{6}}
 \@writefile{toc}{\contentsline {section}{\numberline {4}Intuition Confirm/Change}{6}}
 \newlabel{Intuition Confirm/Change}{{4}{6}}
-\@writefile{toc}{\contentsline {subsection}{\numberline {4.1}Characterizations of Different Packet Types}{6}}
-\newlabel{Characterizations of Different Packet Types}{{4.1}{6}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {4.1}Characterizations of Different Behaviors}{6}}
+\newlabel{Characterizations of Different Behaviors}{{4.1}{6}}
 \@writefile{toc}{\contentsline {section}{\numberline {5}Conclusion}{6}}
 \newlabel{Conclusion}{{5}{6}}
+\bibcite{Leung2008}{1}
+\bibcite{Ellard2003}{2}
+\bibcite{EllardLedlie2003}{3}
 \bibcite{Anderson2004}{4}
 \bibcite{Orosz2013}{5}
 \bibcite{Dabir2008}{6}

TracingPaper.log

@@ -1,4 +1,4 @@
-This is pdfTeX, Version 3.1415926-2.5-1.40.14 (MiKTeX 2.9 64-bit) (preloaded format=pdflatex 2014.12.22)  8 APR 2015 10:04
+This is pdfTeX, Version 3.1415926-2.5-1.40.14 (MiKTeX 2.9 64-bit) (preloaded format=pdflatex 2014.12.22)  8 APR 2015 15:11
 entering extended mode
 **C:/Users/Wortman/Documents/UConn/TracingPaper/TracingPaper.tex
 (C:/Users/Wortman/Documents/UConn/TracingPaper/TracingPaper.tex
@@ -190,60 +190,67 @@ File: omsptm.fd
 LaTeX Font Info:    Font shape `OMS/ptm/m/n' in size <10> not available
 (Font)              Font shape `OMS/cmsy/m/n' tried instead on input line 213.
  [5]
-Underfull \hbox (badness 1077) in paragraph at lines 241--242
-\OT1/ptm/m/n/10 not only pull out in-for-ma-tion per-ta-nent to the
+Underfull \hbox (badness 1221) in paragraph at lines 242--243
+\OT1/ptm/m/n/10 SMB's in-ter-nal man-age-ment would tackle
  []
 
 [6]
-Underfull \hbox (badness 10000) in paragraph at lines 283--284
+Underfull \hbox (badness 1077) in paragraph at lines 265--266
+\OT1/ptm/m/n/10 not only pull out in-for-ma-tion per-ta-nent to the
+ []
+
+
+Underfull \hbox (badness 10000) in paragraph at lines 307--308
 []\OT1/ptm/m/it/10 Common In-ter-net File Sys-tem (CIFS) Pro-
  []
 
 
-Underfull \hbox (badness 10000) in paragraph at lines 283--284
+Underfull \hbox (badness 10000) in paragraph at lines 307--308
 \OT1/ptm/m/it/10 to-col\OT1/ptm/m/n/10 , urlhttp://msdn.microsoft.com/en-
  []
 
 
-Underfull \hbox (badness 10000) in paragraph at lines 285--286
+Underfull \hbox (badness 10000) in paragraph at lines 309--310
 []\OT1/ptm/m/it/10 Server Mes-sage Block (SMB) Pro-to-
  []
 
 
-Underfull \hbox (badness 10000) in paragraph at lines 285--286
+Underfull \hbox (badness 10000) in paragraph at lines 309--310
 \OT1/ptm/m/it/10 col\OT1/ptm/m/n/10 , urlhttp://msdn.microsoft.com/en-
  []
 
 
-Underfull \hbox (badness 10000) in paragraph at lines 300--302
+Underfull \hbox (badness 10000) in paragraph at lines 324--326
 []\OT1/ptm/m/it/10 PF[]RING User Guide\OT1/ptm/m/n/10 , url-
  []
 
 
-Overfull \hbox (61.33023pt too wide) in paragraph at lines 300--302
+Overfull \hbox (61.33023pt too wide) in paragraph at lines 324--326
 \OT1/ptm/m/n/10 https://svn.ntop.org/svn/ntop/trunk/PF[]RING/doc/UsersGuide.pdf
 
  []
 
-[7] (C:\Users\Wortman\Documents\UConn\TracingPaper\TracingPaper.aux) ) 
+[7] [8
+
+] (C:\Users\Wortman\Documents\UConn\TracingPaper\TracingPaper.aux) ) 
 Here is how much of TeX's memory you used:
  1472 strings out of 493705
- 19767 string characters out of 3144563
+ 19764 string characters out of 3144563
  82796 words of memory out of 3000000
  4799 multiletter control sequences out of 15000+200000
  20443 words of font info for 42 fonts, out of 3000000 for 9000
  1025 hyphenation exceptions out of 8191
  34i,8n,21p,2172b,437s stack positions out of 5000i,500n,10000p,200000b,50000s
-{C:/Progr
-am Files/MiKTeX 2.9/fonts/enc/dvips/fontname/8r.enc}<C:/Program Files/MiKTeX 2.
-9/fonts/type1/public/amsfonts/cm/cmsy10.pfb><C:/Program Files/MiKTeX 2.9/fonts/
-type1/urw/courier/ucrr8a.pfb><C:/Program Files/MiKTeX 2.9/fonts/type1/urw/times
-/utmb8a.pfb><C:/Program Files/MiKTeX 2.9/fonts/type1/urw/times/utmbi8a.pfb><C:/
-Program Files/MiKTeX 2.9/fonts/type1/urw/times/utmr8a.pfb><C:/Program Files/MiK
-TeX 2.9/fonts/type1/urw/times/utmri8a.pfb>
-Output written on TracingPaper.pdf (7 pages, 113682 bytes).
+{C:/Program
+ Files/MiKTeX 2.9/fonts/enc/dvips/fontname/8r.enc}<C:/Program Files/MiKTeX 2.9/
+fonts/type1/public/amsfonts/cm/cmsy10.pfb><C:/Program Files/MiKTeX 2.9/fonts/ty
+pe1/urw/courier/ucrr8a.pfb><C:/Program Files/MiKTeX 2.9/fonts/type1/urw/times/u
+tmb8a.pfb><C:/Program Files/MiKTeX 2.9/fonts/type1/urw/times/utmbi8a.pfb><C:/Pr
+ogram Files/MiKTeX 2.9/fonts/type1/urw/times/utmr8a.pfb><C:/Program Files/MiKTe
+X 2.9/fonts/type1/urw/times/utmri8a.pfb>
+Output written on TracingPaper.pdf (8 pages, 116205 bytes).
 PDF statistics:
- 51 PDF objects out of 1000 (max. 8388607)
+ 54 PDF objects out of 1000 (max. 8388607)
  0 named destinations out of 1000 (max. 500000)
  1 words of extra memory for PDF output out of 10000 (max. 10000000)
 

TracingPaper.tex

@@ -225,9 +225,34 @@ When examinging the data produced from this research, one has to look for a limi
 
 \section{Intuition Confirm/Change}
 \label{Intuition Confirm/Change}
+In order ot interpret the data being analyzed and dissected, the first step was to understand how to pair the byte throughput and IO event frequency into an understanding of the system.  This was achieved by including examination of the data relative to the surrounding behavior.  Pairing the information in this manner shows not only the bytes \& IO behavior but preliminary understanding of how much throughput is being generated by each IO event; giving an outline of client behvaior on the system.\\
 
-\subsection{Characterizations of Different Packet Types}
-\label{Characterizations of Different Packet Types}
+Expectation would dicatate that there will be spikes of activity the week leading up the beginning of the semester, the first few days after the semester starts, and during any moments of maintenance that make use of the network; valleys/low points of activity right before (2 days leading up to) the beginning of the semester, holidays (9/1 - labor day), and general progression of less traffic as the semester progresses.  Spikes would be expected to be moments either when new files are being added onto the system (mainly writes), or when a large number of users are attempting to access files (mainly reads).  Ditches would most likely show periods of low to no activity, although both the IO \& Bytes graphs should be examined to confirm inactivity rather than something else.
+
+\subsection{Characterizations of Different Behaviors}
+\label{Characterizations of Different Behaviors}
+Different bahvioral situations (seen using pairing of bytes and IO graphs/behavior) are imaged as follows:
+\textit{Assumptions:}
+\begin{itemize}
+\item Bytes - Amount of data being passed
+\item IOs - Number of interactions occurring on network
+\end{itemize}
+\textit{Combinations:}
+\begin{itemize}
+\item Large number of IO \& Small number of Bytes:
+	\begin{itemize}
+	\item Small number of bytes being pushed over the network \textbf{but} there are a large number of IO events being processed.  If bottlenecks are seen they will most likely be due to management (software?) attempting to deal with the large volume of client interactions.  Race conditions and concerns about "age of request" could be an issue, but ideally OpLocks and SMB's internal management would tackle these issues.
+	\end{itemize}
+\item Small number of IO \& Large number of Bytes:
+	\begin{itemize}
+	\item Few clients interacting \textbf{but} large number of bytes being pushed across the network.  If bottlenecks are seen they will most likely be due to physical limitations of the system; wires, switches, etc.
+	\end{itemize}
+\item Similar number of IO \& number of Bytes:
+	\begin{itemize}
+	\item Both high - High user traffic and throughput.  System is taxed in both aspects; bottlenecks could come from management of clients or from physical limitations of network hardware (e.g. wires).
+	\item Both low - Low user traffic and throughput.  System is at relaxed state; no bottlenecks should be seen.
+	\end{itemize}
+\end{itemize}
 
 \section{Conclusion}
 \label{Conclusion}