I'm not sure what using wget is supposed to show.
Using it 25 times in a row on a completely stable, completely idle 25mbps connection, I get speeds/times that vary by 100% consistently
(IE min is 496k/s, max is 895k/s, average is about 600k/s)
Using wget is a completely useless benchmark, from what I can tell.
Using apache's little benchmark tool I get about 255ms vs 180ms average for 100 requests to each.
The interesting part is that for ajax.googleapis.com I get:
Connection Times (ms)
min mean[+/-sd] median max
Connect: 175 228 28.2 227 306
Processing: 0 12 15.1 8 90
Waiting: 0 0 0.0 0 0
Total: 189 240 29.8 235 350
and for cloudflare I get:
Connection Times (ms)
min mean[+/-sd] median max
Connect: 19 28 13.1 25 125
Processing: 125 155 28.0 146 246
Waiting: 21 28 6.5 27 65
Total: 144 182 30.7 175 271
IE for google, all the time is in actually getting a connection and getting the bits, whereas, for cloudflare, there is actually some time waiting for their servers.
Using 5 concurrent requests actually gives me a massive advantage for google (cloudflare takes roughly the same time, google goes 4 times faster)
(IE min is 496k/s, max is 895k/s, average is about 600k/s)
Using wget is a completely useless benchmark, from what I can tell. Using apache's little benchmark tool I get about 255ms vs 180ms average for 100 requests to each.
The interesting part is that for ajax.googleapis.com I get:
and for cloudflare I get: IE for google, all the time is in actually getting a connection and getting the bits, whereas, for cloudflare, there is actually some time waiting for their servers.Using 5 concurrent requests actually gives me a massive advantage for google (cloudflare takes roughly the same time, google goes 4 times faster)