which machine is in the west coast? the one your tracing on? is that
hget or a web server on plan9? is this the same test as posted by
david?

where do you see out-of-window rxes? what does that even mean?

On 2/23/16, erik quanstrom <quans...@quanstro.net> wrote:
> On Tue Feb 23 09:25:53 PST 2016, 23h...@gmail.com wrote:
>> in the long run the rwin seems much higher (65535) than the number of
>> bytes in flight (less than 3x1500 bytes).
>>
>> i just noticed that the minimum latency numbers seem way low. many
>> latency samples appear at around 40ms and 100ms, but there's also
>> outliers? below 1ms. i don't get how this pcap got produced. perhaps
>> wireshark is also interpreting it wrong, or timestamps are broken...
>
>> > 26/status:Established qin 0 qout 0 rq 0.0 srtt 1256 mdev 628 sst 65535
>> > cwin
>> > 4517 swin 5808>>0 rwin 65535>>4 qscale 0 timer.start 10 timer.count 10
>> > rerecv 0 katimer.start 2400 katimer.count 2400
>>
>> where did you run this?
>
> machine on the us west coast.  clearly we are prevoking some sort of odd
> behavior
> in this machine, but it's not clear to me what we're doing.
>
> the only clue we have is the out-of-window rxes.  perhaps the sender is
> scaling.
>
> - erik
>
>

Reply via email to