Date: Wed, 22 Aug 2007 17:12:28 +0200 From: Claudio Jeker <cjeker@diehard.n-r-g.com> To: freebsd-net@freebsd.org Subject: Re: Route caching ? Message-ID: <20070822151228.GB22194@diehard.n-r-g.com> In-Reply-To: <f85d6aa70708220737p28fb6260h699754544ccd249a@mail.gmail.com> References: <f85d6aa70708220003le893770uca9ceea467d85618@mail.gmail.com> <46CC475F.8030505@FreeBSD.org> <f85d6aa70708220737p28fb6260h699754544ccd249a@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 22, 2007 at 05:37:50PM +0300, Ivo Vachkov wrote: > Actually there is: > > struct route_in6 ip6_forward_rt; > > that "caches" the last route used (thanks blue !!!) but i think this > technique is pointless in a multiflow traffic. > > Is it reasonable to believe that route caches can improve networking > performance or we should leave it up to the routing table itself ? > Just because you believe that route caches are great doesn't mean it is true. Show some real code and include benchmarks with various workloads (e.g. a core router that is hit by many many many sessions). Until now all caching solutions resulted in very bad performance on busy boxes. Remember ip_fastforward or how was it called? Another example are all crapy L3 switches that burn down if the CAM (chache) is flodded. IMO it is better to make the route lookup faster and forget about caching. -- :wq Claudio
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070822151228.GB22194>