mirror of
https://github.com/mofeng-git/One-KVM.git
synced 2025-12-12 09:10:30 +08:00
7f8bb428d3
The existing policy sets dirty_background_bytes to 5, which is erroneously too small that incurs write amplification and read starvations. Considering a raspi with 2 GiB of RAM, this is 43 million times smaller than the default Linux policy, which is 10%. Considering that this will be deployed to mostly read-only system with emphasis on data integrity (hence needing tighter data writeback), set this to 256 KiB. Continuing addressing the overly excessive data writeback policies, also bump the dirty_writeback_centisecs from 250ms to 1000ms. Any dirty data written in the past 1 second will be written to the storage. Signed-off-by: Juhyung Park <qkrwngud825@gmail.com>
11 lines
404 B
Plaintext
11 lines
404 B
Plaintext
# Overly-aggressive data writeback policies to minimize the chance of data corruption
|
|
# Start dirty data writeback when it exceeds 256 KiB or 1s has passed
|
|
vm.dirty_background_bytes = 262144
|
|
vm.dirty_writeback_centisecs = 100
|
|
|
|
# https://groups.google.com/g/meetecho-janus/c/xoWIQfaoJm8
|
|
net.core.rmem_default = 500000
|
|
net.core.wmem_default = 500000
|
|
net.core.rmem_max = 1000000
|
|
net.core.wmem_max = 1000000
|