From: Aki Niimura <akineko@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Network throughput (localhost)
Date: Fri, 13 Mar 2009 00:25:48 -0700 [thread overview]
Message-ID: <59f1f0cb0903130025k31cc2c9fud865dd776534c2bd@mail.gmail.com> (raw)
Hello Linux experts,
I developed a Python program, which tries to take advantage of
available Multi CPU resources.
Two programs (Server and Client) are running in separate processes
communicating each other using Socket IPC.
The performance I'm getting is somewhat in line with my expectation
under Solaris/x86 but significantly slower
under Linux (CentOS 5) even both use the identical hardware.
My investigation revealed that the performance is bottlenecked by the
communication (Socket to localhost).
So, I wrote much simpler program (socket server and socket client) to
measure the network throughput.
What I found was that the network throughput on both platforms
(Solaris/x86 and CentOS Linux) are almost
identical if packets are going out but the network throughput of
Solaris/x86 is almost twice (up to three times)
the throughput Linux can deliver if the packets are destined to localhost.
I know that Solaris treats packets destined to localhost differently.
Because of this, my program is slower (than one process) under Linux
(and is practically useless).
(I see meaningful performance gain under Solaris/x86, though)
I haven't tried any other Linux distributions.
Is there any Linux distribution known for better localhost network throughput?
Is there any way to improve the localhost throughput under Linux (CentOS)?
Of course, some people would point out that other types of IPC (such
as shared memory) are better choices
for the communication between closely coupled multi-processing
program. Unfortunately, there are
reasons that my program needs to use Socket.
Any suggestions will be greatly appreciated.
Best regards,
Aki Niimura
next reply other threads:[~2009-03-13 7:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 7:25 Aki Niimura [this message]
2009-03-13 10:18 ` Bernd Petrovitsch
2009-03-13 17:08 ` David Miller
2009-03-13 18:38 ` Aki Niimura
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=59f1f0cb0903130025k31cc2c9fud865dd776534c2bd@mail.gmail.com \
--to=akineko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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®