public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: latency & real-time-ness.
Date: Sun, 03 Mar 2002 13:12:03 -0700	[thread overview]
Message-ID: <3C828393.7030501@candelatech.com> (raw)

I have been doing some tests with 2.4.19-pre2-ac2 with
regard to network latency.  When running a steady stream of
138byte UDP packets at 115 packets per second, I see about
.1% of the packets take more than 5 miliseconds to go from
user-space to user-space on a 1Ghz PIII machine.

At 50Mbps (bi directional), I see a much wider latency spread,
with some packets taking up to 300ms or higher to get from A
to B.  The CPU load ranges from about 30% to 80% utilization
at this speed...

I'm running the program at nice -18.

So, what kind of things can I do to decrease the latency?

Would the low-latency patch help me?

Are there any scheduling tricks I can use to tell the kernel
that my program should get to run as soon as it wants to?

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>       <Ben_Greear AT excite.com>
President of Candela Technologies Inc      http://www.candelatech.com
ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear



             reply	other threads:[~2002-03-03 20:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-03 20:12 Ben Greear [this message]
2002-03-03 20:55 ` latency & real-time-ness Alan Cox
2002-03-03 22:43   ` Ben Greear
2002-03-04  1:12     ` J Sloan
2002-03-04  3:32       ` Ben Greear
2002-03-04  3:45         ` Robert Love
2002-03-04  4:32         ` J Sloan
2002-03-04 20:01       ` Jussi Laako
2002-03-04  1:09   ` J Sloan
2002-03-04  1:33     ` Alan Cox
2002-03-04  1:37       ` J Sloan
2002-03-04 15:31       ` Erik Andersen
  -- strict thread matches above, loose matches on Subject: below --
2002-03-04 16:20 Dieter Nützel
2002-03-04 18:32 ` Robert Love
2002-03-04 23:48   ` Rik van Riel
2002-03-04 23:56     ` Robert Love

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=3C828393.7030501@candelatech.com \
    --to=greearb@candelatech.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