From: Andrew Morton <akpm@digeo.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Aaron Lehmann <aaronl@vitelus.com>,
Con Kolivas <conman@kolivas.net>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [BENCHMARK] 2.5.47{-mm1} with contest
Date: Tue, 12 Nov 2002 12:59:17 -0800 [thread overview]
Message-ID: <3DD16BA5.DFE01C34@digeo.com> (raw)
In-Reply-To: Pine.LNX.3.96.1021112150713.25274B-100000@gatekeeper.tmr.com
Bill Davidsen wrote:
>
> In the area of things I do do every day, the occasionally posted AIM and
> BYTE benchmarks look as though pipe latency and thruput are down, UNIX
> socket latency and thruput are down, and these are things which will make
> the system feel slower.
Yes, the AIM numbers which have been posted here are quite outrageous.
It's (hopefully) either a few Great Big Bugs or something in 2.5 has
invalidated the measurements. Or, conceivably, the reduction of the
size of the slabs_free list in the slab allocator.
I shall be taking a look at what's going on in there fairly soon.
next prev parent reply other threads:[~2002-11-12 20:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 23:31 [BENCHMARK] 2.5.47{-mm1} with contest Con Kolivas
2002-11-12 0:09 ` Andrew Morton
2002-11-12 1:51 ` Con Kolivas
2002-11-12 2:07 ` mark walters
2002-11-12 2:18 ` Con Kolivas
2002-11-12 8:52 ` Giuliano Pochini
2002-11-12 9:20 ` Jens Axboe
2002-11-12 9:40 ` Con Kolivas
2002-11-12 3:04 ` Aaron Lehmann
2002-11-12 11:04 ` Andrew Morton
2002-11-12 14:20 ` Aaron Lehmann
2002-11-12 14:23 ` Jens Axboe
2002-11-12 20:37 ` Bill Davidsen
2002-11-12 20:59 ` Andrew Morton [this message]
2002-11-20 23:02 ` Andrew Morton
2002-11-21 0:08 ` William Lee Irwin III
2002-11-21 1:11 ` Alan Cox
2002-11-21 6:54 ` Andrew Morton
2002-11-21 13:20 ` Dave Jones
2002-11-21 17:21 ` Andrew Morton
2002-11-21 17:26 ` William Lee Irwin III
2002-11-21 18:18 ` Dave Jones
2002-11-21 18:25 ` Bill Davidsen
2002-11-21 14:00 ` Dave Jones
2002-11-21 19:59 ` Denis Vlasenko
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=3DD16BA5.DFE01C34@digeo.com \
--to=akpm@digeo.com \
--cc=aaronl@vitelus.com \
--cc=conman@kolivas.net \
--cc=davidsen@tmr.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 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.