LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Sen Horak" <sen.horak@gmail.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Performance of concurrent senders
Date: Wed, 7 Feb 2007 10:49:53 -0500	[thread overview]
Message-ID: <a80eebd40702070749t103c2b5qa8ac627eb997056d@mail.gmail.com> (raw)
In-Reply-To: <a80eebd40702061251v54153e7ficdae109111c91a27@mail.gmail.com>

Hi --

I have been running some experiments involving processes sending large
volumes of data concurrently. The results show (on Linux 2.6.19.2)
that although the total throughput achieved by all the processes
remains constant, the jitter increases as the number of processes
increases. Beyond about 64 processes (on a 2.4GHz Xeon with 4Mb of
cache), processes start getting starved and the streams get very
bursty.

Are there any steps one can take to make the jitter scale better, eg.
by using another scheduler? I guess that it is reasonable that the
jitter grow with added contention through the TCP/IP stack - but what
growth rate is acceptable? Is the data I have below reasonable?

The jitter varies as follows and is shown as an average+/- sd across
25 10-second intervals.

Concurrency            Jitter (us)

1                               1.6+/-0.8
2                               1.5+/-1.1
4                               1.4+/-0.6
8                               0.8+/-0.5
12                             2.3+/-1.2
16                             3.3+/-2.1
20                             4.6+/-2.5
24                             6.2+/-1.4
28                             7.8+/-3.2
32                             10.0+/-3.4
64                             100+

Sen

       reply	other threads:[~2007-02-07 15:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a80eebd40702061251v54153e7ficdae109111c91a27@mail.gmail.com>
2007-02-07 15:49 ` Sen Horak [this message]
2007-02-07 18:56   ` David Schwartz

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=a80eebd40702070749t103c2b5qa8ac627eb997056d@mail.gmail.com \
    --to=sen.horak@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Performance of concurrent senders' \
    /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

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).