On Tue, Mar 26, 2013 at 9:46 AM, Arlie Stephens ar...@worldash.org wrote:
On Mar 25 2013, valdis.kletni...@vt.edu wrote:
Just for the record, most of my high-performance stuff runs best with
the noop scheduler - when you're striping I/O across several hundred disks,
the last thing you want is
On Mon, Mar 25, 2013 at 8:17 PM, valdis.kletni...@vt.edu wrote:
On Mon, 25 Mar 2013 17:23:40 -0700, Raymond Jennings said:
Is there some sort of mechanism that throttles the size of the writeback
pool?
There's a lot of tunables in /proc/sys/vm - everything from drop_caches
to swappiness
On Mar 25 2013, valdis.kletni...@vt.edu wrote:
Just for the record, most of my high-performance stuff runs best with
the noop scheduler - when you're striping I/O across several hundred disks,
the last thing you want is some some single-minded disk scheduler re-arranging
the I/Os and
Just curious, is there a cap on how much data can be in writeback at
the same time?
I'm asking because I have over a gigabyte of data in dirty, but
during flush, only about 60k or so is in writeback at any one time.
Is there a cap of sorts, and if so, how do I remove it?
On Mon, 25 Mar 2013 16:33:48 -0700, Raymond Jennings said:
Just curious, is there a cap on how much data can be in writeback at
the same time?
I'm asking because I have over a gigabyte of data in dirty, but
during flush, only about 60k or so is in writeback at any one time.
Only a gigabyte?
On Mon, Mar 25, 2013 at 5:06 PM, valdis.kletni...@vt.edu wrote:
On Mon, 25 Mar 2013 16:33:48 -0700, Raymond Jennings said:
Just curious, is there a cap on how much data can be in writeback at
the same time?
I'm asking because I have over a gigabyte of data in dirty, but
during flush, only
On Mon, 25 Mar 2013 17:23:40 -0700, Raymond Jennings said:
Is there some sort of mechanism that throttles the size of the writeback pool?
There's a lot of tunables in /proc/sys/vm - everything from drop_caches
to swappiness to vfs_cache_pressure. Note that they all interact in mystical
and
