From: "J.R. Mauro" <jrm8005@gmail.com>
To: "David Miller" <davem@davemloft.net>
Cc: olafvdspek@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: Unix sockets via TCP on localhost: is TCP slower?
Date: Thu, 13 Nov 2008 19:27:22 -0500 [thread overview]
Message-ID: <3aaafc130811131627l52fcb3a0jba5cc566844fc89e@mail.gmail.com> (raw)
In-Reply-To: <20081113.162233.39564490.davem@davemloft.net>
On Thu, Nov 13, 2008 at 7:22 PM, David Miller <davem@davemloft.net> wrote:
> From: "J.R. Mauro" <jrm8005@gmail.com>
> Date: Thu, 13 Nov 2008 19:19:36 -0500
>
>> On Wed, Nov 12, 2008 at 6:20 PM, Olaf van der Spek <olafvdspek@gmail.com> wrote:
>> > Hi,
>> >
>> > Quite often in discussions, I see people claiming Unix sockets are
>> > faster then TCP sockets on a connection that stays inside localhost.
>>
>> Unix domain sockets should be faster because they're not subject to
>> windowing, ACKs, flow control, encapsulation, etc. etc.
>
> And the wakeup rate is higher for TCP, and our process scheduler has
> been getting gradually slower and slower over time since 2.6.22
>
I'm not sure about this, but I now also remember reading somewhere
that TCP has an extra context switch, but I don't know if what I read
was about Linux or a totally different OS.
next prev parent reply other threads:[~2008-11-14 0:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 23:20 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
2008-11-14 0:19 ` J.R. Mauro
2008-11-14 0:22 ` David Miller
2008-11-14 0:27 ` J.R. Mauro [this message]
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=3aaafc130811131627l52fcb3a0jba5cc566844fc89e@mail.gmail.com \
--to=jrm8005@gmail.com \
--cc=davem@davemloft.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®