netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: Netchannels: progress report. Sending benchmark.
Date: Mon, 10 Jul 2006 17:32:45 +0400	[thread overview]
Message-ID: <20060710133244.GA32193@2ka.mipt.ru> (raw)
In-Reply-To: <20060710132321.GA585@2ka.mipt.ru>

On Mon, Jul 10, 2006 at 05:23:21PM +0400, Evgeniy Polyakov (johnpol@2ka.mipt.ru) wrote:
> After week vacations I'm pleased to announce following progress report.
> 
> Numbers for small packets (80 bytes) bulk sending:
> 
>  * netchannel: 57 MB/sec, ~80% CPU usage
>  * socket: 22 MB/sec, ~90% CPU usage
> 
> Receiving side is netcat server, which dumps received data into
> /dev/null
> 
> Actually it is not 100% correct to call that results correct, since 
> it uses hackish optimisations, which can lead to broken behaviour for 
> non-bulk transfers or transfers over bad lines. If some of them are
> removed, speed drops to 54 MB/sec for 80 bytes packets, and if socket
> analog for NODELAY flag is set, i.e. each packet is immediately being
> sent when it has been written, speed drops down to 16 MB/sec (socket
> with SO_NODELAY was not tested though).

I mean TCP_NODELAY.
Socket code uses nonblocking mode and epoll.

-- 
	Evgeniy Polyakov

      reply	other threads:[~2006-07-10 13:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08 17:15 Netchannels: netchannel vs. socket. 2:0 Evgeniy Polyakov
2006-06-08 17:40 ` Evgeniy Polyakov
2006-06-08 23:00 ` Hans Henrik Happe
2006-06-09  5:09   ` Evgeniy Polyakov
2006-06-13 17:33 ` Netchannels: alternative TCP/IP stack? Evgeniy Polyakov
2006-06-29  9:38   ` Netchannels: progress report Evgeniy Polyakov
2006-06-29 17:19     ` James Morris
2006-06-29 18:15       ` Evgeniy Polyakov
2006-07-10 13:23     ` Netchannels: progress report. Sending benchmark Evgeniy Polyakov
2006-07-10 13:32       ` Evgeniy Polyakov [this message]

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=20060710133244.GA32193@2ka.mipt.ru \
    --to=johnpol@2ka.mipt.ru \
    --cc=davem@davemloft.net \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).