On 06/07/14 23:24, Andy Furniss wrote:
Alan Goodman wrote:
http://www.thinkbroadband.com/speedtest/results.html?id=140466829057682641064
A further thought, having just reminded my self how long the TBB speed
test upload takes -
If you were using sfq on upload it looks like the spikes correspond well
with perturb 10. Historically sfqs hash was quite weak, so perturb was
usefull, but it got changed to jhash ages ago so is less needed, or at
least not that short, as it causes packet reordering leading to a bit of
disruption.
If you weren't using sfq for up then ignore the above :-) it's possible
that I am out of date WRT sfq reordering and it has been fixed.
--
To unsubscribe from this list: send the line "unsubscribe lartc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
I had also noticed the rhthmic nature in the ping roundtrip also.
I have tried removing perturb it doesnt appear to make much difference
on either front.
My htb based script also dies in a fiery mess with the excessive p2p test.
I have three gut feelings at the moment:
Firstly, With massive flow counts - at least for bittorent - the amount
of small packets being uploaded is effectively saturating the upload.
Secondly, as flow counts continue to increase upload is becoming
insufficient to keep up with the rate of small packets which is causing
the massive latency spike I am seeing.
Thirdly, my classifier might be missing some of the important ACK
packets... Should packets like the one listed below be getting prioritised?
IN=eth1 OUT= MAC=00:a0:c9:81:c9:d5:f0:de:f1:f8:83:52:08:00
SRC=192.168.25.41 DST=5.9.123.39 LEN=52 TOS=0x00 PREC=0x00 TTL=64
ID=54864 DF PROTO=TCP SPT=51413 DPT=39415 WINDOW=1379 RES=0x00 ACK URGP=0
Many thanks everybody for all the extremely valuable input received so
far, I think we're just about on the home straight now!
Alan
--
To unsubscribe from this list: send the line "unsubscribe lartc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html