next up previous
Next: Related Work Up: Measuring Proxy Performance with Previous: Effect of Adding Disk

Effect of Low Bandwidth Client-Connections

We were also interested in analysing the impact of low bandwidth connections on proxy performance. We wanted to analyse how proxies behave when they must handle requests sent by several clients, using slow connections, such as modems. We used a modem emulator [2] which introduces delays to each IP packet transmitted in order to achieve a certain effective bandwidth that is smaller than the one provided by the network connection. This modem emulator, implemented in the Linux operating system, assigns to each process a predefined maximum bandwidth that it can use. The default bandwidth used in our experiments is 28.8Kbps for each process. We used the WPB to measure the performance of the four proxy servers included in our testbed when requests were sent by clients running on top of this modified version of Linux. We spread 30 clients over three DEC Celebris XL590 90 MHz Pentium machines with 32 MB of main memory each and standard 10 Mbps Ethernet card. We spawn 20 WPB server processes on two COW nodes. We compare the results for these experiments with those collected when the same number of clients were spread over the same machines running an unmodified Linux. The network connecting clients and proxies is non-dedicated and includes one router in the path.

Tables  5 and  6 show the results obtained for all four proxies. No errors were observed during the experiments for any proxy server. It is clear that the low bandwidth effect dominates. The latency increases by more than a factor of 2 for all proxies. It is also interesting to notice that the difference between the latencies observed in the first and second phases is smaller for the low bandwidth connection. This reflects the fact that the time spent in the communication between client and proxy is the dominant factor in the overall performance and it is much more important than the delay introduced by misses in the cache, since the connections between servers and proxy is much faster in our setup. The decrease in the hit ratio is also noteworthy, especially for Apache and Proxy N. Observing the results collected by iostat and vmstat, it is clear that the bottleneck is the transmission in the network. Despite the shorter service time, disk throughput is lower for the experiments with low bandwidth. The utilization of both disk and cpu is much lower for the 28Kbps bandwidth experiment and, as consequence, the overall proxy throughput degrades.


 
Table 5:   The effect of low bandwidth connections on Squid and Proxy N performance.
3|c|Squid    
Metric 28Kbps bandwidth 10 Mbps bandwidth
First phase latency (s) 12.13 (7%) 4.74 (1%)
Second phase latency (s) 13.19 (42%) 2.45 (2%)
Hit Ratio 25.01 (0.5%) 25.11 (0.4%)
Byte Hit Ratio 21.36 (61%) 19.58 (19%)
reads/s 2.44 (51%) 6.68 (3%)
writes/s 6.10 (57%) 26.67 (8%)
svc_t (ms) 65.11 (45%) 182.76 (5%)
disk busy(%) 11.53 (54%) 45.3 (4%)
cpu idle(%) 97.98 (1%) 81.78 (2%)
cpu user (%) 0.51 (65%) 5.56 (6%)
cpu system (%) 1.46 (60%) 12.68 (8%)
3|c|Proxy N    
Metric 28Kbps bandwidth 10 Mbps bandwidth
First phase latency (s) 13.66 (15%) 5.02 (13%)
Second phase latency (s) 10.39 (9%) 4.29 (67%)
Hit Ratio 15.24 (2%) 20.86 (9%)
Byte Hit Ratio 11.30 (2%) 17.95 (8%)
reads/s 1.48 (56%) 6.06 (8%)
writes/s 17.22 (11%) 50.80 (23%)
svc_t (ms) 110.86 (6%) 155.78 (13%)
disk busy(%) 25.52 (14%) 83.19 (20%)
cpu idle(%) 95.06 (0.7%) 79.66 (7%)
cpu user (%) 1.07 (21%) 5.99 (25%)
cpu system (%) 3.79 (11%) 14.36 (27%)


 
Table 6:   The effect of low bandwidth connection on Cern and Apache performance.
3|c|Cern    
Metric 28Kbps bandwidth 10 Mbps bandwidth
First phase latency (s) 12.61 (4%) 4.98 (21%)
Second phase latency (s) 11.19 (21%) 2.92 (7%)
Hit Ratio 19.12 (24%) 22.98 (7%)
Byte Hit Ratio 15.59 (38%) 18.26 (9%)
reads/s 0.27 (21%) 1.18 (85%)
writes/s 13.64 (10%) 35.48 (85%)
svc_t (ms) 63.49 (9%) 78.36 (72%)
disk busy(%) 19.50 (13%) 53.99 (87%)
cpu idle(%) 87.12 (3%) 30.79 (18%)
cpu user (%) 2.68 (32%) 15.50 (13%)
cpu system (%) 10.16 (18%) 53.69 (7%)
3|c|Apache    
Metric 28Kbps bandwidth 10 Mbps bandwidth
First phase latency (s) 10.78 (4%) 5.51 (42%)
Second phase latency (s) 9.75 (7%) 3.00 (20%)
Hit Ratio 12.89 (4%) 26.06 (40%)
Byte Hit Ratio 8.84 (25%) 18.07 (51%)
reads/s 6.58 (3%) 9.48 (52%)
writes/s 11.31 (57%) 33.64 (76%)
svc_t (ms) 55.46 (43%) 115.64 (12%)
disk busy(%) 26.93 (35%) 65.62 (47%)
cpu idle(%) 94.05 (1%) 78.50 (6%)
cpu user (%) 0.64 (26%) 2.98 (32%)
cpu system (%) 5.27 (17%) 18.58 (21%)


next up previous
Next: Related Work Up: Measuring Proxy Performance with Previous: Effect of Adding Disk
Pei Cao
4/13/1998