Work out kernel parameter sizing instantly with clear inputs, formula shown and shareable results.
vm.dirty_ratio caps how much page cache may hold unwritten data before writers are blocked, and on a large-memory system the default 20 percent can be many gigabytes — which takes tens of seconds to flush and produces long write stalls. Sizing it so a full flush completes in a few seconds is the usual fix on database and log-heavy servers.
Kernel sizing
fs.file-max ~ 3 x concurrent connections; dirty bytes = RAM x dirty_ratio; flush time = dirty bytes / disk write throughput
When dirty pages reach dirty_ratio the kernel blocks the writing process until enough data is flushed. With gigabytes of dirty data and a slow disk that pause is measured in seconds.
On large-memory machines yes. An absolute byte limit is independent of RAM size and gives predictable flush duration.