summaryrefslogtreecommitdiffstats
path: root/net/disk_cache
diff options
context:
space:
mode:
authorjar@chromium.org <jar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-03-19 00:59:01 +0000
committerjar@chromium.org <jar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-03-19 00:59:01 +0000
commiteee51b3c5f60f19f2394dba82403c010f7f252f6 (patch)
treeda0751fbf009cdbd4c1849d1a1793dfade5437ee /net/disk_cache
parent0b9a1cc9c1ed9892d451ca3e3bb7795c72aedd03 (diff)
downloadchromium_src-eee51b3c5f60f19f2394dba82403c010f7f252f6.zip
chromium_src-eee51b3c5f60f19f2394dba82403c010f7f252f6.tar.gz
chromium_src-eee51b3c5f60f19f2394dba82403c010f7f252f6.tar.bz2
Try to get inter-packet times more precisely
I had tried to rely on the call to ReadData() being made once per TCP/IP packet, but histograms from the field show that does not work well :-(. This version looks for boundary counts of multiples of 1430 bytes, and uses that as a better approximation of when a packet is received. For test data with only a few packets, this is excellent. Some vendors such as Google tend to use at most 1430 bytes per packet, so even if we are off a bit, it will be close (for small packet counts). Alos, add histogram for total transmitted data (compressed via sdch and gzip) r=huanr,ajenjo Review URL: http://codereview.chromium.org/48077 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12069 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'net/disk_cache')
0 files changed, 0 insertions, 0 deletions