默认情况下关闭Linux OOM杀手?

前端之家收集整理的这篇文章主要介绍了默认情况下关闭Linux OOM杀手?前端之家小编觉得挺不错的,现在分享给大家,也给大家做个参考。
Linux上的OOM杀手每隔一段时间就会对各种应用程序造成严重破坏,而且似乎在内核开发方面并没有做太多改进.作为设置新服务器时的最佳做法,将内存过度使用的默认设置反转,即将其关闭(vm.overcommit_memory = 2),除非您知道要将其用于特定用途,否则它会不会更好?那些用例是什么,你知道你想要过度使用?

作为奖励,因为在vm.overcommit_memory = 2的情况下的行为取决于vm.overcommit_ratio和交换空间,对于后两者的大小调整以使整个设置保持合理运行将是一个很好的经验法则吗?

解决方法

一个有趣的比喻(从 http://lwn.net/Articles/104179/):

An aircraft company discovered that it was cheaper to fly its planes with less fuel on board. The planes would be lighter and use less fuel and money was saved. On rare occasions however the amount of fuel was insufficient,and the plane would crash. This problem was solved by the engineers of the company by the development of a special OOF (out-of-fuel) mechanism. In emergency cases a passenger was selected and thrown out of the plane. (When necessary,the procedure was repeated.) A large body of theory was developed and many publications were devoted to the problem of properly selecting the victim to be ejected. Should the victim be chosen at random? Or should one choose the heaviest person? Or the oldest? Should passengers pay in order not to be ejected,so that the victim would be the poorest on board? And if for example the heaviest person was chosen,should there be a special exception in case that was the pilot? Should first class passengers be exempted? Now that the OOF mechanism existed,it would be activated every now and then,and eject passengers even when there was no fuel shortage. The engineers are still studying precisely how this malfunction is caused.

原文链接:/linux/402568.html

猜你在找的Linux相关文章