Charles Randall said:
>
> Out of 128M of ram, it's swapped nearly everything else out to keep 85M of
> this 400M file in ram, even though it will never touch it again. :)
>
> I see two possible fixes for this. One could be madvise'ing periodically
> with MADV_DONTNEED. If I understand correctly, this would help a bit, right?
>
> Or, mmap smaller regions of the file, and keep moving the buffer. This would
> also help with files exceeding mmap's limits.
>
>
> Any thoughts?
>
Unless the ability has been removed recently, setting the physical
memory soft limit can help a very little bit also:
bash> ulimit -m 16384
can make a program a little more friendly to it's neighbors. The
soft (in both senses) limit is mushy, but provides some hints when
paging ensues.
--
John | Never try to teach a pig to sing,
[EMAIL PROTECTED] | it makes one look stupid
[EMAIL PROTECTED] | and it irritates the pig.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
