All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Fisher <bug-track@fisher-privat.net>
To: Sitsofe Wheeler <sitsofe@yahoo.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: smart cache. ist is possible?
Date: Sun, 15 Mar 2009 23:06:34 +0100	[thread overview]
Message-ID: <49BD7BEA.50307@fisher-privat.net> (raw)
In-Reply-To: <20090315181315.GA4369@silver.sucs.org>

Hi,

Sitsofe Wheeler schrieb:
> Hi,
> 
> On Sun, Mar 15, 2009 at 04:28:55PM +0100, Alexey Fisher wrote:
>> I found for my self how great is cache in linux. If read one file from
>> disk, so i don't need to do it second time, chace will do the job. It
>> speed up thing greatly. But i found it not working with realy big files.
>> Like i have 4GB RAM, so if i read a file like 4.6GB, cache won't work.
> 
> Watch out - if you are doing cache tests you really want to be using
> drop_caches ( http://linux-mm.org/Drop_Caches ) before your "cold" runs
> so you can be sure that the cache really was empty before you started...
> 

It is not what i mean. I know how to clear cache but exactly i do not 
won't it. I will use cache and it's working perfectly with small files. 
But there is a problem with big files. For example i have 4GB RAM, if i 
read 4,6GB file the cache is useless. The question is; are there any way 
to workaround it, except more RAM?

  reply	other threads:[~2009-03-15 22:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-15 15:28 smart cache. ist is possible? Alexey Fisher
2009-03-15 18:13 ` Sitsofe Wheeler
2009-03-15 22:06   ` Alexey Fisher [this message]
2009-03-15 23:26     ` Sitsofe Wheeler
2009-03-16  7:34       ` Alexey Fisher
2009-03-16 17:36         ` Sitsofe Wheeler
2009-03-15 22:23 ` Dave Chinner
2009-03-16 13:02 ` Pádraig Brady
2009-03-16 15:15 ` Paulo Marques

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=49BD7BEA.50307@fisher-privat.net \
    --to=bug-track@fisher-privat.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sitsofe@yahoo.com \
    /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.