Cliff Wells said:
Actually a very good idea. Why have RAM sitting unused?
So that some is available when (not if) you need more!
Ah, but one of the fundamental features of cached files is that they're already on disk, and don't need to be swapped. If space is needed, it's least expensive to simply forget about a few files, and read them again when they're needed. Application data pages have to get pretty old before they're swapped out in favor of leaving cached files in RAM.
Does that clarify why using the maximum amount of memory for file caching is a good thing?
...As root, run: /sbin/sysctl -w vm.bdflush="30 500 0 0 2560 15360 60 20 0"
Execellent!
However, could you please explain how these changes might help? I'm asking through ignorance, not disbelief.
It will allow the kernel to process write buffers less often, which means that you may get more reads, and better interactive performance. It's dependant on the use of the system, so only your own testing will tell you if it's a gain or loss.
-- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
