> I understand that auto-balancing code that deals with all
> situations is very hard to design; so let me share my experience
> on other Unix systems (from a user/administrator point of view):
>
> I have used Unix systems (mainly HPUX) for several years as personal
> workstations or servers and buffer cache usage were very differents:
>
> On workstations, you are mainly looking for fast interactive response
> time and you want to dedicate as much memory as possible to running
> processes so limiting buffer cache to 10% of physical memory (these
> workstations had typically 32 - 64 Mb of RAM) was good.
"Unfortunately" the cache also contains _process memory_ in
Linux. Limiting the cache to 10% also means limiting the
code size of all your processes to something smaller than
that.
Also, read-in swap pages are in the so-called swap cache,
which is also part of the page cache.
This means that simple limits on cache size probably won't do
much good on Linux.
regards,
Rik
-- Virtual memory is like a game you can't win; However, without VM there's truly nothing to lose...http://www.surriel.com/ http://www.conectiva.com/ http://distro.conectiva.com.br/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/