Date: Fri, 02 Feb 2001 09:51:22 +0900 From: itojun@iijlab.net To: Yu-Shun Wang <yushunwa@isi.edu> Cc: freebsd-net@freebsd.org Subject: Re: IPComp question Message-ID: <22229.981075082@coconut.itojun.org> In-Reply-To: yushunwa's message of Thu, 01 Feb 2001 15:48:37 PST. <Pine.BSF.4.31.0102011540120.1012-100000@amc.isi.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> Another (sort of) related question: I've got the bandwidth > measurements for different algorthms using netperf. I was > really surprised that IPComp did so bad. Any ideas? thanks for measurements, it's good to see. i guess couple of reasons here. - because we compress short packets with IPComp, we cannot make a good use of compression history/dictionary. we always initialize everything on every packet, and it can consume cpu time. - zlib buffer management - it has ring buffer management on both in/output ends, because we will see data stream with different sizes. - zlib memory management - heavy use of malloc? itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?22229.981075082>