Здравствуйте, Gt_, Вы писали:


S>>>>Ты тогда уж все варианты приведи а не только фигурную цитату тог что лично тебе понравилось
Gt_>>>мне не понравилось то что ты полез с советами не подозревая, что есть целый ряд ситуаций, где отсутствие свопа оправдано.
S>>Например? Опиши свою.
Gt_>я уже объяснял, из-за zookeeper
У него про swap другое написано:

Set the Java heap size. This is very important to avoid swapping, which will seriously degrade ZooKeeper performance. To determine the correct value, use load tests, and make sure you are well below the usage limit that would cause you to swap. Be conservative — use a maximum heap size of 3GB for a 4GB machine.
...
Do not put ZooKeeper in a situation that can cause a swap. In order for ZooKeeper to function with any sort of timeliness, it simply cannot be allowed to swap. Therefore, make certain that the maximum heap size given to ZooKeeper is not bigger than the amount of real memory available to ZooKeeper. For more on this, see Things to Avoid below.
...
You should take special care to set your Java max heap size correctly. In particular, you should not create a situation in which ZooKeeper swaps to disk. The disk is death to ZooKeeper. Everything is ordered, so if processing one request swaps the disk, all other queued requests will probably do the same. the disk. DON'T SWAP.
Be conservative in your estimates: if you have 4G of RAM, do not set the Java max heap size to 6G or even 4G. For example, it is more likely you would use a 3G heap for a 4G machine, as the operating system and the cache also need memory. The best and only recommend practice for estimating the heap size your system needs is to run load tests, and then make sure you are well below the usage limit that would cause the system to swap.

Там нет рекомендация отключать своп. Напротив, там рекомендации подтюнить размер кучи