4.3. Evaluation

We evaluated techniques described in this chapter using a trace driven simulation study. This trace was generated synthetically using a Poisson arrival pattern. In all simulations presented in this section, we assumed a single media type with 4 Mb/s bandwidth requirement and a block size of 0.5 Mbytes (Tp = 1 second). Blocks were distributed across twenty Quantum Atlas XP32150 disks using random. Our repository consisted of 50 different edited clips each consisting of 120 logical blocks. We assumed a uniform distribution of access to the clips.

All results demonstrate that the hiccup probability decreases as a function of N (number of buffers), see Figure 4.5.a. For example, we can reduce the hiccup probability to less than one in a million by increasing the number of buffers to seven. This probability implies that a hiccup only happens approximately once in 12 days when a client continuously displays clips. This would be satisfactory for almost all applications.

Figure 4.5. Startup latency distribution of PB techniques.

(a) Hiccup probability.

(b) Avg.startup latency (N=7).


Table 4.2 shows that Skip provides a lower hiccup probability than Wait because Skip minimizes the server's load by not servicing requests that have already violated their deadlines. This difference becomes more profound when the number of buffers decreases because this increases the percentage of requests that miss their deadline. It is important to note that the use of Skip is application dependent. Those applications that can tolerate skipping content should use Skip in order to minimize the probability of hiccup. For the rest of this evaluation, we assume the Wait scheme.

Table 4.2. Skip vs. Wait (utilization = 0.807).
 SchemesNumber of buffers (N)
234567
Avg. retrieval time (msec)Skip296.4338.7348.8351.9352.6352.6
Wait336.6347.9351.9352.4352.6352.6
Hiccup probabilitySkip0.0113880.0011950.0002380.0000430.000002< 10–b
Wait0.0426480.0054850.001064 00002120.000005< 10–b

Table 4.3 shows a comparison of alternative PB techniques. The results demonstrate that the probability of hiccups is almost identical with all techniques. Figure 4.5.b and 4.6.a show the average startup latency and the worst latency as a function of N. Figure 4.6.b shows the distribution of startup latency when N=7. The y-axis of this figure is the probability of a display incurring a certain startup latency. For example, the peak point of PBV-AD illustrates that 44% of displays experience startup latency between 100 msec and 150 msec. The aggressive display (AD) approach provides a better startup latency distribution, i.e., a smaller average and variance, than the conservative display (CD) approach. Overall, both PBV-AD and PBF-AD are superior to the other alternatives when it comes to startup latency. Hence, this can satisfy almost all the latency-sensitive applications, even in the worst case scenario (336 msec), with a hiccup probability that is less than one in a million (< 10–6).

Figure 4.6. Startup latency distribution of PB techniques.

(a) Worst startup latency.

(b) Startup latency distribution (N=7).


Table 4.3. PB techniques (utilization = 0.807).
 SchemesNumber of buffers (N)
234567
Avg. retrieval time (msec)PBF-CD335.7348.1352.5354.3355.4357.1
PBF-AD335.7348.1352.7354.3355.6357.0
PBV-CD335.7347.8350.5352.7353.8355.9
PBV-AD335.7347.7352.5354.0355.6357.3
Hiccup probabilityPBF-CD0.0413640.0055740.0012000.0002930.000027< 10–6
PBF-AD0.0413640.0055980.0012130.0002810.000023< 10–6
PBV-CD0.0413640.0052760.0011150.0001960.000021< 10–6
PBV-AD0.0413640.0056810.0012120.0002610.000021< 10–6
Avg. startup latency (msec)PBF-CD318.2186.6148.7195.9206.2224.2
PBF-AD318.2148.5140.5139.4138.5139.8
PBV-CD318.2369.0375.3380.1389.8420.6
PBV-AD318.3147.7139.5138.1136.9137.7
Standard deviation of startup latencyPBF-CD281.7144.293.559.548.352.9
PBF-AD281.7106.065.448.040.740.5
PBV-CD281.7325.3334.6326.2327.5351.2
PBV-AD281.7103.864.445.138.137.4
Worst startup latency (msec)PBF-CD2861270824301883881512
PBF-AD2861253425241999980406
PBV-CD286135154409437347405087
PBV-AD2861255224371828891336

Similar trends were observed with our other simulation studies that utilized different parameters such as utilization, block size, number of disks. Generally, a lower hiccup probability is observed when the system utilization is lower. The number of disks does not impact the performance unless it is too small (less than 6). With a smaller block size, the portion of disk seek time becomes greater and it results in a higher disk utilization and a lower hiccup probability.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.133.109.211