Changes between Version 35 and Version 36 of PerformanceTesting


Ignore:
Timestamp:
11/18/11 15:58:19 (12 years ago)
Author:
Samuli Seppänen
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PerformanceTesting

    v35 v36  
    133133All EC2 instances were created to the same availability zone (us-east-1d). The setup of 100 client instances took ~4 minutes with 34 threads running Fabric (~3 runs per thread).
    134134
    135 == MP-1 results ==
    136 
    137 === OpenVPN 2.2.1/m1.small/UDP/IPv4/OpenSSL/5 clients (MP-1) ===
    138 
    139 '''Test name:''' 07-mp1-m1.small-openvpn221
    140 
    141 '''Connection establishment'''
    142 
    143 Insignificant CPU load when all clients (5) connected.
    144 
    145 '''Client statistics'''
    146 
    147 ||'''Test'''||'''Subtest'''||'''Host'''||'''Clients'''||'''Total transfer (MB)'''||'''Total bandwidth (MB/s)'''||'''Average bandwidth (MB/s)'''||
    148 ||07-mp1-m1.small-openvpn221||10s||average||5||148.9||15.56||3.11||
    149 ||07-mp1-m1.small-openvpn221||30s||average||5||440.4||15.38||3.08||
    150 ||07-mp1-m1.small-openvpn221||60s||average||5||888.8||15.51||3.1||
    151 
    152 '''Server statistics'''
    153 
    154 ||'''Test'''||'''Subtest'''||'''CPU usr (%)'''||'''CPU sys (%)'''||'''CPU total (%)'''||'''CPU wait (%)'''||
    155 ||07-mp1-m1.small-openvpn221||10s||29.2981||41.9214||89.374||0||
    156 ||07-mp1-m1.small-openvpn221||30s||32.9692||48.3951||94.4449||0.060871||
    157 ||07-mp1-m1.small-openvpn221||60s||35.8375||48.7774||97.0125||0||
    158 
    159 '''Analysis'''
    160 
    161 OpenVPN 2.2.1 on an Amazon EC2 m1.small instance can handle 5 OpenVPN client instances well.
    162 
    163 == MP-2 results ==
    164 
    165 === OpenVPN 2.2.1/m1.small/UDP/IPv4/OpenSSL/20 clients (MP-2) ===
    166 
    167 '''Test name:'''  13-mp2-m1.small-openvpn221
    168 
    169 '''Connection establishment'''
    170 
    171 Test repeated twice due to timing issues:
    172 
    173  * First run: CPU usage 29-33% for 2 seconds when all clients (20) connected at the same time (at 12:22:02-12:22:03).
    174  * Second run: CPU usage 100% for 2 seconds...
    175 
    176 '''Client statistics'''
    177 
    178 ||'''Test'''||'''Subtest'''||'''Host'''||'''Clients'''||'''Total transfer (MB)'''||'''Total bandwidth (MB/s)'''||'''Average bandwidth (MB/s)'''||
    179 ||13-mp2-m1.small-openvpn221||10s||average||20||177.22||16.53||0.8265||
    180 ||13-mp2-m1.small-openvpn221||30s||average||20||474.95||14.72||0.736||
    181 ||13-mp2-m1.small-openvpn221||60s||average||19||829.02||12.56||0.661053||
    182 
    183 '''Server statistics'''
    184 
    185 ||'''Test'''||'''Subtest'''||'''Real length'''||'''CPU usr (%)'''||'''CPU sys (%)'''||'''CPU total (%)'''||'''CPU wait (%)'''||
    186 ||13-mp2-m1.small-openvpn221||10s||21||24.6989||54.91||97.7355||0||
    187 ||13-mp2-m1.small-openvpn221||30s||56||26.3991||54.5965||96.4954||0||
    188 ||13-mp2-m1.small-openvpn221||60s||98||26.0081||56.4454||97.1554||0||
    189 
    190 '''Analysis'''
    191 
    192 OpenVPN 2.2.1 on an Amazon EC2 m1.small instance seems to be able to handle 20 OpenVPN clients fairly well.
    193 
    194 === OpenVPN 2.2.1/m1.large/UDP/IPv4/OpenSSL/20 clients (MP-2) ===
    195 
    196 '''Test names:'''
    197 
    198  * 16-mp2-m1.large-openvpn221
    199  * 18-mp2-m1.large-openvpn221
    200  * 19-mp2-m1.large-openvpn221
    201  * 20-mp2-m1.large-openvpn221
    202 
    203 '''Connection establishment'''
    204 
    205 During all tests the client initialization phase took 1-2 seconds, judging from server's CPU load and network traffic levels. CPU utilization was  2-6% during this period. 
    206 
    207 '''Client statistics'''
    208 
    209 ||'''Test'''||'''Subtest'''||'''Host'''||'''Clients'''||'''Total transfer (MB)'''||'''Total bandwidth (MB/s)'''||'''Average bandwidth (MB/s)'''||
    210 ||16-mp2-m1.large-openvpn221||10s||average||19||386.42||37.06||1.95053||
    211 ||16-mp2-m1.large-openvpn221||30s||average||20||339.85||9.27||0.4635||
    212 ||16-mp2-m1.large-openvpn221||60s||average||20||1168.61||18.91||0.9455||
    213 ||18-mp2-m1.large-openvpn221||10s||average||20||275.55||26.54||1.327||
    214 ||18-mp2-m1.large-openvpn221||30s||average||20||741.01||23.8||1.19||
    215 ||18-mp2-m1.large-openvpn221||60s||average||20||1176.57||18.78||0.939||
    216 ||19-mp2-m1.large-openvpn221||120s||average||14||2323.11||18.96||1.35429||
    217 ||20-mp2-m1.large-openvpn221||120s||average||17||2369.42||19.28||1.13412||
    218 
    219 '''Server statistics'''
    220 
    221 ||'''Test'''||'''Subtest'''||'''Real length'''||'''CPU usr (%)'''||'''CPU sys (%)'''||'''CPU total (%)'''||'''CPU wait (%)'''||
    222 ||16-mp2-m1.large-openvpn221||10s||22||8.34841||14.974||32.1606||0.0163636||
    223 ||16-mp2-m1.large-openvpn221||30s||72||8.82207||15.8551||30.9363||0.00511111||
    224 ||16-mp2-m1.large-openvpn221||60s||72||8.73214||15.6736||31.3002||0.252833||
    225 ||18-mp2-m1.large-openvpn221||10s||16||7.90512||15.4132||34.4907||0||
    226 ||18-mp2-m1.large-openvpn221||30s||41||8.6408||15.4649||31.9355||0.241415||
    227 ||18-mp2-m1.large-openvpn221||60s||65||8.66112||15.8789||31.0061||0.0868||
    228 ||19-mp2-m1.large-openvpn221||120s||132||9.18264||15.7622||31.2403||0.104886||
    229 ||20-mp2-m1.large-openvpn221||120s||132||9.15555||15.8739||30.8286||0.0837879||
    230 
    231 '''Analysis'''
    232 
    233 A ''m1.large'' instance can easily handle 20 clients. As tests were more precisely timed (with "at") than in earlier MP-2 tests (which used chained commands with "sleep" in between), the overly long test periods must have been caused by the iperf server not being able to handle client connections quickly enough.
    234 
    235135=== OpenVPN 2.2.1/m1.large/UDP/IPv4/OpenSSL/20 clients (MP-2) ===
    236136