mirror of
https://github.com/archr-linux/Arch-R.git
synced 2026-03-31 14:41:55 -07:00
35 lines
1.3 KiB
Diff
35 lines
1.3 KiB
Diff
The default dirty ratio is chosen to be a compromise between throughput and
|
|
overall system latency. On a desktop, if an application writes to disk a lot,
|
|
that application should be the one to slow down rather than the desktop as a
|
|
whole. At higher dirty ratio settings, an application could write a lot to
|
|
disk and then happily use lots of CPU time after that while the rest of the
|
|
system is busy waiting on that naughty applications disk writes to complete
|
|
before anything else happening.
|
|
|
|
Lower ratios mean that the application that do a lot of disk writes end up
|
|
being responsible for their own actions and they're the ones that slow down
|
|
rather than the system in general.
|
|
|
|
This does decrease overall write throughput slightly, but to the benefit of
|
|
the latency of the system as a whole.
|
|
|
|
-ck
|
|
|
|
---
|
|
mm/page-writeback.c | 2 +-
|
|
1 file changed, 1 insertion(+), 1 deletion(-)
|
|
|
|
Index: linux-2.6.37-ck2/mm/page-writeback.c
|
|
===================================================================
|
|
--- linux-2.6.37-ck2.orig/mm/page-writeback.c 2011-01-06 14:04:10.000000000 +1100
|
|
+++ linux-2.6.37-ck2/mm/page-writeback.c 2011-02-14 10:11:10.037252000 +1100
|
|
@@ -78,7 +78,7 @@
|
|
/*
|
|
* The generator of dirty data starts writeback at this percentage
|
|
*/
|
|
-int vm_dirty_ratio = 20;
|
|
+int vm_dirty_ratio = 5;
|
|
|
|
/*
|
|
* vm_dirty_bytes starts at 0 (disabled) so that it is a function of
|