From owner-freebsd-net@FreeBSD.ORG Mon Nov 14 06:54:45 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA14D106564A for ; Mon, 14 Nov 2011 06:54:45 +0000 (UTC) (envelope-from weiler@soe.ucsc.edu) Received: from mail-01.cse.ucsc.edu (mail-01.cse.ucsc.edu [128.114.48.32]) by mx1.freebsd.org (Postfix) with ESMTP id B35998FC14 for ; Mon, 14 Nov 2011 06:54:45 +0000 (UTC) Received: from erich-weilers-macbook-pro.local (50-0-69-3.dsl.static.fusionbroadband.com [50.0.69.3]) by mail-01.cse.ucsc.edu (Postfix) with ESMTPSA id 5B97C1009C69; Sun, 13 Nov 2011 22:54:45 -0800 (PST) Message-ID: <4EC0BB34.3020600@soe.ucsc.edu> Date: Sun, 13 Nov 2011 22:54:44 -0800 From: Erich Weiler User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Matt Connor References: <4EC033B7.5080609@soe.ucsc.edu> "<4EC0395C.3030302@swin.edu.au>" <4EC055CB.40100@soe.ucsc.edu> "<4EC0585F.5000104@soe.ucsc.edu>" <4EC05F58.1050103@soe.ucsc.edu> <4EC072CB.5030800@freebsd.org> <9898624e64a38e5e860591d194ec5c70@www1.xerq.net> In-Reply-To: <9898624e64a38e5e860591d194ec5c70@www1.xerq.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Arg. TCP slow start killing me. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2011 06:54:45 -0000 > 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.