diff --git a/TracingPaper.aux b/TracingPaper.aux index 35b281b..bef1e92 100644 --- a/TracingPaper.aux +++ b/TracingPaper.aux @@ -79,16 +79,6 @@ \bibcite{EllardLedlie2003}{3} \bibcite{Anderson2004}{4} \bibcite{Orosz2013}{5} -\bibcite{Dabir2008}{6} -\bibcite{Narayan2010}{7} -\bibcite{Skopko2012}{8} -\bibcite{MS-CIFS}{9} -\bibcite{MS-SMB}{10} -\bibcite{MS-SMB2}{11} -\bibcite{Roselli2000}{12} -\bibcite{Vogels1999}{13} -\bibcite{Meyer2012}{14} -\bibcite{PFRING}{15} \@writefile{toc}{\contentsline {subsection}{\numberline {4.3}Run Patterns}{5}} \newlabel{Run Patterns}{{4.3}{5}} \@writefile{toc}{\contentsline {subsection}{\numberline {4.4}Locating Performance Bottlenecks}{5}} @@ -103,6 +93,16 @@ \newlabel{Characterizations of Different Packet Types}{{5.1}{5}} \@writefile{toc}{\contentsline {section}{\numberline {6}Conclusion}{5}} \newlabel{Conclusion}{{6}{5}} +\bibcite{Dabir2008}{6} +\bibcite{Narayan2010}{7} +\bibcite{Skopko2012}{8} +\bibcite{MS-CIFS}{9} +\bibcite{MS-SMB}{10} +\bibcite{MS-SMB2}{11} +\bibcite{Roselli2000}{12} +\bibcite{Vogels1999}{13} +\bibcite{Meyer2012}{14} +\bibcite{PFRING}{15} \bibcite{Traeger2008}{16} \bibcite{Kavalanekar2009}{17} \bibcite{Douceur1999}{18} diff --git a/TracingPaper.log b/TracingPaper.log index 2fdfb0f..349a215 100644 --- a/TracingPaper.log +++ b/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.20) 4 JAN 2015 15:17 +This is pdfTeX, Version 3.1415926-2.5-1.40.14 (MiKTeX 2.9 64-bit) (preloaded format=pdflatex 2014.12.20) 10 JAN 2015 13:30 entering extended mode **TracingPaper.tex (C:\UConn\TracingPaper\TracingPaper.tex @@ -169,48 +169,60 @@ Underfull \hbox (badness 2269) in paragraph at lines 102--103 LaTeX Font Info: Font shape `OT1/ptm/bx/it' in size <10> not available (Font) Font shape `OT1/ptm/b/it' tried instead on input line 157. [4] -Underfull \hbox (badness 10000) in paragraph at lines 380--381 +LaTeX Font Info: Try loading font information for OMS+ptm on input line 353. + + ("C:\Program Files\MiKTeX 2.9\tex\latex\psnfss\omsptm.fd" +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 353. + +Underfull \hbox (badness 1077) in paragraph at lines 355--356 +\OT1/ptm/m/n/10 not only pull out in-for-ma-tion per-ta-nent to the + [] + +[5] +Underfull \hbox (badness 10000) in paragraph at lines 389--390 []\OT1/ptm/m/it/10 Common In-ter-net File Sys-tem (CIFS) Pro- [] -Underfull \hbox (badness 10000) in paragraph at lines 380--381 +Underfull \hbox (badness 10000) in paragraph at lines 389--390 \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 382--383 +Underfull \hbox (badness 10000) in paragraph at lines 391--392 []\OT1/ptm/m/it/10 Server Mes-sage Block (SMB) Pro-to- [] -Underfull \hbox (badness 10000) in paragraph at lines 382--383 +Underfull \hbox (badness 10000) in paragraph at lines 391--392 \OT1/ptm/m/it/10 col\OT1/ptm/m/n/10 , urlhttp://msdn.microsoft.com/en- [] -[5] [6 - -] (C:\UConn\TracingPaper\TracingPaper.aux) +[6] (C:\UConn\TracingPaper\TracingPaper.aux) LaTeX Warning: There were multiply-defined labels. ) Here is how much of TeX's memory you used: - 1454 strings out of 493705 - 19238 string characters out of 3144575 + 1471 strings out of 493705 + 19526 string characters out of 3144575 82851 words of memory out of 3000000 - 4784 multiletter control sequences out of 15000+200000 + 4798 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,1884b,437s stack positions out of 5000i,500n,10000p,200000b,50000s {C:/Program Files/MiKTeX 2.9/fonts/enc/dvips/fontname/8r.enc} -Output written on TracingPaper.pdf (6 pages, 95725 bytes). +s/MiKTeX 2.9/fonts/type1/public/amsfonts/cm/cmsy10.pfb> +Output written on TracingPaper.pdf (6 pages, 104849 bytes). PDF statistics: - 42 PDF objects out of 1000 (max. 8388607) + 46 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) diff --git a/TracingPaper.pdf b/TracingPaper.pdf index d566632..a9c2203 100644 Binary files a/TracingPaper.pdf and b/TracingPaper.pdf differ diff --git a/TracingPaper.synctex.gz b/TracingPaper.synctex.gz index 0123b34..7925031 100644 Binary files a/TracingPaper.synctex.gz and b/TracingPaper.synctex.gz differ diff --git a/TracingPaper.tex b/TracingPaper.tex index 46369a6..1fa8d7a 100644 --- a/TracingPaper.tex +++ b/TracingPaper.tex @@ -346,6 +346,15 @@ All comands sent over the network are coupled to an identifying MID/PID/TID/UID \section{Conclusion} \label{Conclusion} \textit{Do the results show a continuation in the trend of traditional computer science workloads?} +On the outset of this work it was believed that the data collected and analyzed would follow similar behavior patterns seen in previous papers \textit{Cite?}. Our initial results were confusing and most definitely did not meet expections. One of these oddities was that during the day one would see a greater increase in writes instead of reads. The frist assumption was that this is due to the system and how users interact with everything. +I belive that the greater number of writes comes from students doing intro work for different classes in which students are constantly saving their work while reading instructions from a single source. One must also recall that this data itself has limited interpretation because only a small three week windows of infomration is being examined. A better, and far more complete, image can be constructed using data captured from the following months, or more ideally, from an entire year's worth of data. An other limitation of the results is the scope of the analysis is curbed and does not yet fully dissect all of the fields being passed in network communication. +The future work of this project would be to +\begin{itemize} + \item 1. Complete the dissection analysis to include all captured fields from the originating pcap files. + \item 2. All DataSeries files (which are purposed for distribution) would be a single file per day's worth of communication; this may be possible with new additions to the DataSeries code but pcap limitations do not currently allow for this. + \item 3. Modulation of the capturing software would not only pull out information pertanent to the SMB/CIFS protocol, but would be able to pull multiple protocols which a user would be able to define prior to run-time. + \item 4. Better automation of the capturing system would remove the potential of human error cause loss of data. Use of new DataSeries tools may allow for recovery of previously corrupted DataSeries files. +\end{itemize} %references section %\bibliographystyle{plain}