All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chris Friesen" <cfriesen@nortel.com>
To: Olaf van der Spek <olafvdspek@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Unix sockets via TCP on localhost: is TCP slower?
Date: Thu, 13 Nov 2008 17:04:28 -0600	[thread overview]
Message-ID: <491CB27C.3090606@nortel.com> (raw)
In-Reply-To: <b2cc26e40811131106g7a1c46d0y89d24b11cb0570fb@mail.gmail.com>

Olaf van der Spek wrote:
> On Thu, Nov 13, 2008 at 12:24 PM, Arnaldo Carvalho de Melo
> <acme@redhat.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.

Lmbench shows local tcp as noticeably slower than unix sockets on a Mac 
G5 running 2.6.27.


*Local* Communication latencies in microseconds - smaller is better
---------------------------------------------------------------
Host           OS 2p/0K  Pipe AF     UDP  RPC/   TCP  RPC/ TCP
                   ctxsw       UNIX         UDP         TCP conn
--------- ------- ----- ----- ---- ----- ----- ----- ----- ----
localhost 2.6.27  2.270  10.5 12.6  19.9  31.5  22.7  35.5  68.




*Local* Communication bandwidths in MB/s - bigger is better
-----------------------------------------------------------------------
Host          OS  Pipe AF    TCP  File   Mmap  Bcopy  Bcopy  Mem   Mem
                        UNIX      reread reread (libc) (hand) read write
--------- ------- ---- ---- ---- ------ ------ ------ ------ ---- -----
localhost 2.6.27  1368 1564 334. 1111.8 2068.8  930.3  947.0 2072 1269.




Chris

  reply	other threads:[~2008-11-13 23:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-12 23:20 Unix sockets via TCP on localhost: is TCP slower? Olaf van der Spek
2008-11-13 11:24 ` Arnaldo Carvalho de Melo
2008-11-13 19:06   ` Olaf van der Spek
2008-11-13 23:04     ` Chris Friesen [this message]
2008-11-14  0:19 ` J.R. Mauro
2008-11-14  0:22   ` David Miller
2008-11-14  0:27     ` J.R. Mauro
2008-11-14  8:51   ` Olaf van der Spek
2008-11-14  8:54     ` Eric Dumazet
2008-11-14  9:06       ` Olaf van der Spek
2008-11-14 13:14         ` J.R. Mauro
2008-11-14  8:56     ` David Miller
2008-11-14  9:09       ` Olaf van der Spek
2008-11-14 10:37         ` Bernd Petrovitsch
2008-11-14 13:17         ` J.R. Mauro
2008-11-14 21:07         ` Willy Tarreau
2008-11-14 22:40           ` Olaf van der Spek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=491CB27C.3090606@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=acme@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olafvdspek@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.