Linux version 2.6.32-573.7.1.el6.x86_64 (mockbuild@x86-031.build.eng.bos.redhat.commailto:mockbuild@x86-031.build.eng.bos.redhat.com) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-16) (GCC) ) #1 SMP
vm.dirty_background_ratio = 10 vm.dirty_background_bytes = 0 vm.dirty_ratio = 20 vm.dirty_bytes = 0 vm.dirty_writeback_centisecs = 500 vm.dirty_expire_centisecs = 3000
On Oct 26, 2015, at 1:31 PM, Massimo.Sala@asl.bergamo.itmailto:Massimo.Sala@asl.bergamo.it wrote:
Johnson, Edward A. : Turned out to be a balance issue between the number of pollers, the vm.dirty_background_ratio, and the vm.dirty_ratio.
If I recollect, many distro come "teaked" for end-users, so with both values too high with plenty of RAM servers.
Usually on servers that aren't file server, I set :
vm.dirty_background_bytes=67108864 vm.dirty_ratio=10
Edward, can you specify your sysctl values, kernel, distro that are not so good for that server ?
There are many different configs, I think it is useful to report the "guts" of the problem.
best regards, Sala
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium