Results 1 - 10
of
10,117
Table 5.4: Flow Duration Statistics of P2P and Web Application Mean Median Std. Dev. IQR Skewness
2007
Table 5.5: Flow Duration Statistics of BitTorrent and Gnutella Application Mean Median Std. Dev. IQR Skewness
2007
TABLE VII CORRELATION BETWEEN SIZE AND RATE FOR DIFFERENT PROTOCOL, FLOW SIZES AND DURATION
TABLE VII CORRELATION BETWEEN SIZE AND RATE FOR DIFFERENT PROTOCOL, FLOW SIZES AND DURATION
Table 1: Relative durations of the main subtasks of a work- flow project
1999
Cited by 5
TABLE I EXPECTED NUMBER OF FLOWS F AND BYTES ESTIMATOR MEAN SQUARE ERROR V FROM SAMPLING A SINGLE FLOW OF DURATION t, k PACKETS AND b BYTES, WITH FLOW TIMEOUT T. THE FUNCTION f IS DEFINED IN (19). Vlb AND Vnu ARE DEFINED IN SECTION III-B.5
2005
Cited by 23
TABLE IV. FLOWS STATISTICS WITH DIFFERENT PRIORITIES Flow Loss % Delay ms Average session duration
Table 4 lists the ten applications / traffic flows together with their dependencies, bandwidth requirements, durations and starting times.
"... In PAGE 11: ... Table4... ..."
(Table 6). Table 6 Averaged flood durations and number of days of storm flows after peaks based
"... In PAGE 20: ... 3.4 Comparison of flood durations in urbanized and undeveloped watersheds Flood durations and the number of days of storm flow after peak discharge were compiled for eight watersheds (Table6 ). The number of events analyzed ranged from a ... In PAGE 21: ...tation record. Storm events (annual peak events) in four urban watersheds lasted 3.22 days on average, which was about 0.9 days shorter than that experienced in non-urban watersheds (Table6 ). The average length of storm flows after the peak flow was recorded 1.... In PAGE 21: ...aried from 1.6 to 2.3 days in urban watersheds and 1.2 to 2.0 days in non-urban watersheds (Table6 ). These values are a function of the watershed area size and the key result here is that normalized number of days after peaks was shorter in urban watersheds than those in non-urban watersheds.... ..."
Table 4: Results comparing Adaptive Netflow and Flow Slices with different Slice durations. The total number of packets are about 35 Million.
2005
"... In PAGE 12: ... This also allows for a fairer comparison between the two schemes as the final aggregates instead of individual flows are usually most important for traffic analysis. Table4 illustrates the comparison of error obtained by Adaptive NetFlow and Flow Slices both for packet counts and byte counts. Clearly, in the first group of flows that are larger than 1% of the total traffic volume, Flow Slices performs slightly better than Adaptive Net- Flow.... In PAGE 12: ... Finally, as expected for really small flows, sample and hold based algorithms perform better than ordinary sampling and we can see that Flow Slices performs better than Adaptive NetFlow by almost 7-13%. In the second part of the Table4 , we show how Adap- tive NetFlow and Flow Slices estimated the individ- ual traffic breakdown for common traffic types such as WWW, Email etc. Both Flow Slices and Adaptive Net- Flow estimated close to the actual packet counts for Mail, News, Web traffic, SSH and FTP.... ..."
Cited by 7
Results 1 - 10
of
10,117