| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <b2cc26e40811131106g7a1c46d0y89d24b11cb0570fb@mail.gmail.com> Date: Thu, 13 Nov 2008 20:06:58 +0100 From: "Olaf van der Spek" <olafvdspek@...il.com> To: "Arnaldo Carvalho de Melo" <acme@...hat.com>, "Olaf van der Spek" <olafvdspek@...il.com>, "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org> Subject: Re: Unix sockets via TCP on localhost: is TCP slower? On Thu, Nov 13, 2008 at 12:24 PM, Arnaldo Carvalho de Melo <acme@...hat.com> wrote: > Em Thu, Nov 13, 2008 at 12:20:44AM +0100, Olaf van der Spek escreveu: >> Hi, >> >> Quite often in discussions, I see people claiming Unix sockets are >> faster then TCP sockets on a connection that stays inside localhost. >> Let's say from app A to app B. >> Is this indeed the case and if so, how much and why? >> My assumption is that the kernel can optimize the 'connection' and let >> any performance differences disappear. > > How much? Please measure. I can't be the first one to wonder about this. Has nobody done this kind of benchmark before? > Faster? Not necessarily, Nagle comes to mind, Eh, wouldn't that make TCP slower instead of faster? > among others. What kind of traffic? That matters too. > > Start here: http://en.wikipedia.org/wiki/Nagle's_algorithm Eh, I assume that algorithm is disabled on localhost. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists