There are several IO-bound applications running on my PC (with 4 GB RAM), and by writing as much as I can I want to avoid my SSD
in the file /etc/sysctl.conf file:
vm.dirty_background_ratio = 75 Vm.dirty_ratio = 90 Vm.dirty_expire_centisecs = 360000 vm.swappiness = 0 and in / etc / fstab I have committed = 3600 Parameter added. According to the command
Free , my PCs are usually used by applications with 1 GB RAM and approximately 2500 rams available so with my settings, I actually write on the disk Without being able to write at least 1500-2000 MB data
I did some tests with Medium Writing (300MB - 1000MB) and Free and cat / proc / meminfo | I have noticed that Grep is filthy that they write a few times later (very little that dirty_expire_centisecs time), go below a value next to dirty byte 0.
I suspect that the machine is not near the Om status till the operation cache is read and I want to write dirty to ignore my sysctl.conf settings. Is forced (correct me if my hypothesis is wrong). So the question is: Is it simply unable to read caching (AAAIIM is not possible), or at least change the policy to the page cache, giving more priority to writing cache, so that in reading the cache Flushing could not be compelled to write (maybe kernel source code tweaking ...)? I know that I can easily solve this problem, such as AFFs or overlays like tmpfs or union-fs, but I want to avoid them for a number of reasons.
Sorry for my bad english, I hope you understand my question. Thank you.
Comments
Post a Comment