From: Bill Davidsen <davidsen@tmr.com>
To: Christian Borntraeger <linux-kernel@borntraeger.net>
Cc: linux-kernel@vger.kernel.org, "John Bradford" <john@grabjohn.com>,
"Rik van Riel" <riel@redhat.com>,
"Lasse Kärkkäinen / Tronic" <tronic2@sci.fi>
Subject: Re: Some thoughts about cache and swap
Date: Wed, 09 Jun 2004 15:45:32 -0400 [thread overview]
Message-ID: <40C768DC.4080202@tmr.com> (raw)
In-Reply-To: <200406061038.29470.linux-kernel@borntraeger.net>
Christian Borntraeger wrote:
> John Bradford wrote:
>
>>Quote from Rik van Riel <riel@redhat.com>:
>>
>>>I wonder if we should just bite the bullet and implement
>>>LIRS, ARC or CART for Linux. These replacement algorithms
>>>should pretty much detect by themselves which pages are
>>>being used again (within a reasonable time) and which pages
>>>aren't.
>>
>>Is there really much performance to be gained from tuning the 'limited'
>>cache space, or will it just hurt as many or more systems than it helps?
>
>
> Thats a very good question.
> Most of the time the current algorithm works quite well.
> On the other hand, I definitely know what people mean when they complain
> about cachingand all this stuff. By just copying a big file that I dont use
> afterwards or watching an video I have 2 wonderful scenarios. The cache is
> filled with useless information and big parts of KDE are neither in memory
> nor in cache. Applications could use madvice or other things to indicate
> that they dont need this file a second time, but they usually dont.
>
> I think it might be interesting to have some kind of benchmark, similiar to
> the interactive benchmark of Con that just triggers the workload so many
> people are complaining. If I find the time, I will give it a try in the
> next days.
You might find my response test program useful. My web server is in
three pieces at the moment, but http://pages.prodigy.net/davidsen has a
copy. You might want to do your own, but mine does show the results of
i/o pushing out programs.
--
-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-06-09 19:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-05 14:40 Some thoughts about cache and swap Lasse Kärkkäinen / Tronic
2004-06-05 23:37 ` Rik van Riel
2004-06-06 7:08 ` John Bradford
2004-06-06 8:38 ` Christian Borntraeger
2004-06-09 18:13 ` Matt Mackall
2004-06-09 19:32 ` John Bradford
2004-06-09 19:32 ` Rik van Riel
2004-06-11 14:07 ` Jörn Engel
2004-06-12 1:50 ` Rik van Riel
2004-06-09 19:45 ` Bill Davidsen [this message]
2004-06-09 19:43 ` Bill Davidsen
2004-06-10 7:47 ` Buddy Lumpkin
2004-06-16 14:15 ` jlnance
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=40C768DC.4080202@tmr.com \
--to=davidsen@tmr.com \
--cc=john@grabjohn.com \
--cc=linux-kernel@borntraeger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--cc=tronic2@sci.fi \
/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