From: Shawn Bohrer <shawn.bohrer@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>, Peter Zijlstra <peterz@infradead.org>
Subject: High scheduler wake up times
Date: Sat, 30 Jan 2010 17:45:51 -0600 [thread overview]
Message-ID: <20100130234551.GA27390@mediacenter.gateway.2wire.net> (raw)
Hello,
Currently we have a workload that depends on around 50 processes that
wake up 1000 times a second do a small amount of work and go back to
sleep. This works great on RHEL 5 (2.6.18-164.6.1.el5), but on recent
kernels we are unable to achieve 1000 iterations per second. Using
the simple test application below on RHEL 5 2.6.18-164.6.1.el5 I can run
500 of these processes on and still achieve 999.99 iterations per
second. Running just 10 of these processes on the same machine with
2.6.32.6 produces results like:
...
Iterations Per Sec: 905.659667
Iterations Per Sec: 805.099068
Iterations Per Sec: 925.195578
Iterations Per Sec: 759.310773
Iterations Per Sec: 702.849261
Iterations Per Sec: 782.157292
Iterations Per Sec: 917.138031
Iterations Per Sec: 834.770391
Iterations Per Sec: 850.543755
...
I've tried playing with some of the cfs tunables in /proc/sys/kernel/
without success. Are there any suggestions on how to achieve the
results we are looking for using a recent kernel?
Thanks,
Shawn
#include <sys/epoll.h>
#include <sys/time.h>
#include <stdio.h>
#include <unistd.h>
int main ()
{
int epfd = epoll_create(1);
int i, j;
struct timeval tv;
unsigned long start, end;
const unsigned int count = 60000;
while (1) {
gettimeofday(&tv, NULL);
start = tv.tv_sec * 1000000 + tv.tv_usec;
for (i = 0; i < count; ++i) {
if (epoll_wait(epfd, 0, 1, 1) == -1)
perror("epoll failed");
for (j = 0; j < 10000; ++j)
/* simulate work */;
}
gettimeofday(&tv, NULL);
end = tv.tv_sec * 1000000 + tv.tv_usec;
printf("Iterations Per Sec: %f\n", count/((double)(end - start)/1000000));
}
close(epfd);
}
next reply other threads:[~2010-01-30 23:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-30 23:45 Shawn Bohrer [this message]
2010-01-30 23:56 ` Arjan van de Ven
2010-01-31 0:29 ` Shawn Bohrer
2010-01-31 0:02 ` Arjan van de Ven
2010-01-31 0:11 ` Arjan van de Ven
2010-01-31 0:35 ` Shawn Bohrer
2010-01-31 0:46 ` Shawn Bohrer
2010-01-31 0:47 ` Arjan van de Ven
2010-01-31 3:47 ` Shawn Bohrer
2010-01-31 18:28 ` Arjan van de Ven
2010-01-31 20:50 ` Shawn Bohrer
2010-02-01 8:51 ` Peter Zijlstra
2010-02-01 19:37 ` Shawn Bohrer
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=20100130234551.GA27390@mediacenter.gateway.2wire.net \
--to=shawn.bohrer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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®