All of lore.kernel.org
 help / color / mirror / Atom feed
From: michi1@michaelblizek.twilightparadox.com (michi1 at michaelblizek.twilightparadox.com)
To: kernelnewbies@lists.kernelnewbies.org
Subject: epoll improvements
Date: Fri, 17 Oct 2014 18:47:09 +0200	[thread overview]
Message-ID: <20141017164708.GA4289@grml> (raw)
In-Reply-To: <47342.1413478933@turing-police.cc.vt.edu>

Hi!

On 13:02 Thu 16 Oct     , Valdis.Kletnieks at vt.edu wrote:
> On Thu, 16 Oct 2014 14:09:05 +0200, "Nev Ikte" said:
> 
> > I've tried to reproduce it with a single client
> > and basically, if ep_poll() is able to find an event or the timeout is 0,
> > the latency is down to 5usec, otherwise if it enters the waitqueue
> > the latency goes up to 10-25usec, which impact the application performance.
> 
> Is it possible that what you're actually measuring here is your CPU's
> latency coming out of a sleep state if every task is in a wait queue?

I have seen wakeup latencies of ~100usec on some systems. You may want to
disable sleep states and see of performance gets better. Take a look at:

Documentation/power/pm_qos_interface.txt

Also, you probably want disable frequency scaling:

/sys/devices/system/cpu/cpu.../cpufreq/scaling_governor should return
"performance" for every cpu. You can change it with
eche "performance" > /sys/...

	-Michi
-- 
programing a layer 3+4 network protocol for mesh networks
see http://michaelblizek.twilightparadox.com

      reply	other threads:[~2014-10-17 16:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16 12:09 epoll improvements Nev Ikte
2014-10-16 12:17 ` Greg KH
2014-10-16 12:48   ` Jason Ball
2014-10-16 17:02 ` Valdis.Kletnieks at vt.edu
2014-10-17 16:47   ` michi1 at michaelblizek.twilightparadox.com [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=20141017164708.GA4289@grml \
    --to=michi1@michaelblizek.twilightparadox.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.