Date: Sun, 13 Nov 2011 22:54:44 -0800 From: Erich Weiler <weiler@soe.ucsc.edu> To: Matt Connor <bsd@xerq.net> Cc: freebsd-net@freebsd.org Subject: Re: Arg. TCP slow start killing me. Message-ID: <4EC0BB34.3020600@soe.ucsc.edu> In-Reply-To: <9898624e64a38e5e860591d194ec5c70@www1.xerq.net> References: <4EC033B7.5080609@soe.ucsc.edu> "<4EC0395C.3030302@swin.edu.au>" <4EC055CB.40100@soe.ucsc.edu> "<4EC0585F.5000104@soe.ucsc.edu>" <CAAAm0r0TO5ifZ_-s%2BJEN5jwRNuZQq=8t6zRRKSnfPBTO2Rb%2Bng@mail.gmail.com> <4EC05F58.1050103@soe.ucsc.edu> <4EC072CB.5030800@freebsd.org> <9898624e64a38e5e860591d194ec5c70@www1.xerq.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> Have you considered empty ACK prioritization? I implemented this a year > ago on a pair of production edge routers and noticed significant > improvement on throughput. I have production code examples if you > require them, but this link should be more than enough to get you started: Fascinating. pfSense does have traffic shaping options, among them ACK prioritization and queues. Let me play with that a bit. Totally could be affecting me - my downstream traffic could be great enough to crows out ACKs, thus causing the TCP stream resets. Sounds plausible, at least.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EC0BB34.3020600>