The hoster analyzed the operation of the server
Here is the conclusion:
Right now I see that the server has failed in swap by 1.2GB.
Those. its used swap file is almost the same size as RAM.
KiB Mem : 1873912 total, 168868 free, 1347888 used, 357156 buff/cache
^^^^^^^^^^^^^
KiB Swap: 2621432 total, 1399812 free, 1221620 used. 416200 availMem
^^^^^^^^^^^^^^
This is not a normal state.
Ideal - when the swap file is not used.
Permissible - when less than a quarter of the amount of RAM is used.
Rebooted mysql - paging file usage dropped by 4/5.
did # swapoff -a ; swapon
The server unloaded the swap into memory, and reset it to zero.
Those. top now looks like this
KiB Mem : 1873912 total, 198040 free, 1049884 used, 625988 buff/cache
KiB Swap: 2621432 total, 2621432 free, 0 used. 565292 availMem
Conclusion - mysql is configured to work in a system where there is significantly more than 2G of RAM,
and tries to keep too much information in memory (in the cache), so that the cache ends up on disk. And from this presence of a cache it only gets worse.
Conclusion:
It is necessary to configure mysql in the direction of reducing the size of the cache.
It turns out that the server is somehow incorrectly configured, that is, the database itself
1. Why is this done and what can be done?
2. Perhaps this is somehow connected with the procedure that I run
https://baza.cn.ua/admin/shop/workflow/9/procedure/49/?status=0?Since she has been working for a very long time and can it somehow influence this?