From: Bill Davidsen <davidsen@tmr.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Benchmarking objrmap under memory pressure
Date: Thu, 22 Apr 2004 15:54:25 -0400 [thread overview]
Message-ID: <408822F1.80409@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0404151746140.9558-100000@localhost.localdomain>
Hugh Dickins wrote:
> On Thu, 15 Apr 2004, Bill Davidsen wrote:
>
>>Hugh Dickins wrote:
>>
>>>The worst that will happen with anonmm's mremap move, is that some
>>>app might go slower and need more swap. Unlikely, but agreed possible.
>>
>>It appears that users on small memory machines running kde are not of
>>concern to you. Unfortunately that describes a fair number of people,
>>not everyone has the big memory fast system. I will try to get some
>>reproducible numbers, but "consistently feels faster" is a reason to
>>keep running -aa even if I can't quantify it.
>
>
> Appearances can be deceptive. Of course I care about users,
> of small or large memory machines, running kde or not.
>
> It appears that you do not understand that we're talking about a
> case so rare that we've never seen it in practice, only by testing.
>
> But perhaps we haven't looked out for it enough (no printk), I'd better
> put something in to tell us when it does occur, thanks for the reminder.
>
> If -aa consistently feels faster to you, great, go with it:
> but I doubt it's because of this issue we're discussing!
I don't disagree on that, but it seems that KDE developers have put some
serious effort into making the software well-behaved, and unless there
is some measurable benefit from the code which negates the benefits of
that effort, it seems desirable to appreciate code code by letting it work.
I was more commenting on the good performance at the bottom end than
addressing the large machines. All the big machines I have are in the
overkill range, and finding small benefits doesn't do much with
production loads, so I can't contribute any useful info at that end.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2004-04-22 19:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 7:39 Benchmarking objrmap under memory pressure Martin J. Bligh
2004-04-13 7:51 ` Andrew Morton
2004-04-13 7:55 ` Martin J. Bligh
2004-04-13 21:59 ` Andrea Arcangeli
2004-04-14 0:38 ` Martin J. Bligh
2004-04-14 16:27 ` Andrea Arcangeli
2004-04-14 16:42 ` Martin J. Bligh
2004-04-14 17:11 ` Andrea Arcangeli
2004-04-14 17:48 ` Hugh Dickins
2004-04-14 23:39 ` Andrea Arcangeli
2004-04-15 10:21 ` Hugh Dickins
2004-04-15 13:22 ` Andrea Arcangeli
2004-04-15 13:45 ` Hugh Dickins
2004-04-15 14:08 ` Andrea Arcangeli
2004-04-15 16:23 ` Bill Davidsen
2004-04-15 16:48 ` Hugh Dickins
2004-04-22 19:54 ` Bill Davidsen [this message]
2004-04-22 21:26 ` Hugh Dickins
2004-04-14 18:11 ` Bill Davidsen
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=408822F1.80409@tmr.com \
--to=davidsen@tmr.com \
--cc=hugh@veritas.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