Re: NFS Buffering

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On Wed, Sep 29, 2010 at 8:27 AM, Ian Chapman
<[email protected]> wrote:
> On 29/09/10 22:51, Simon Andrews wrote:
>> That sounds like it might be an answer.  It's a shame there's no way to
>> specify this per-process, but this machine does have quite a bit of RAM
>> in it, so having this specified as a percentage of RAM might make it
>> larger than we'd want.
>> I'll have a play and see what effect this has.
> No problem, there's also a good page here which explains a bit more how
> all this works, as well as some explanation on other tunables that might
> suit you better.
> --

If you have a lot of ram you can boot with a kernel flag
that specifies a smaller memory resource.


You can write a program that gobbles a lot of memory
(compare malloc(); calloc()).   Running a memory hog
can trigger IO of dirty pages out to disk or trigger
a the high/low water mark used to trigger IO.  This works
because at the OS level all of free memory can be used
by the OS as a buffer of one type or another.

The nice thing about a littlepiggie program is that
you can run it from user space and also adjust
how much memory it grabs and when so you can tune
things to your liking.  When you kill it you quickly
get all the memory back.

        T o m   M i t c h e l l
users mailing list
[email protected]
To unsubscribe or change subscription options:

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux