On Tue, Sep 1, 2015 at 7:21 PM, Mel Gorman <mgorman@suse.de> wrote:
On Fri, Aug 28, 2015 at 12:01:11PM -0700, Linda A. Walsh wrote:
Michal Kubecek wrote:
On Friday 28 of August 2015 10:34:48 Navin Parakkal wrote:
On Fri, Aug 28, 2015 at 9:20 AM, Jeff Mahoney <jeffm@suse.com> wrote:
1) Inertia i'll skip this one.
Well, you shouldn't. To change things, one should have good reason. The more intrusive the change, the stronger the arguments for it should be. Unless there is a substantial gain, the change is not worth the effort and the risk.
====
The problem doesn't occur with Oracle systems because during backup they have ways to use direct I/O and many DBAs set that by default . Sounds like a good thing to do because backup is like read source and write dest in both in direct I/O. Your buffer caches hardly grow but when you don't you explicity specify direct i/o when you copy files of huge size like 1000 files of 1G or 10000 files of 100 MB , the buffer_head and ext4_inode_cache or xfs_inode_cache grows very fast. When you are backing up TeraBytes of data ie full export and backup , i think it is better not to fill up the kernel caches that you are going to seldom use. Any thoughts on this ? -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org