Why does 1s save the configuration on a Linux server for a long time?

Question

1C-Enterprise

Installed 1C server on Centos + base on postgres. 1C server, clients and configuration of the latest releases.
Remote access via internet. The base is clean.
I run the configurator on windows, I start loading the UNF configuration (400 mb) - it takes about 3-4 hours to load.
At the same time, the connection with the server is excellent, files of such volumes are uploaded in a few minutes.
After loading the configuration, I click update configuration and hangs again for a couple of hours.
Any change to the configuration and its further saving causes hourly waits.
I repeat, clean base.
With these expectations, the load on the server increases only by 10%, the processor is loaded by 10-15%, and the disks are also slightly loaded.
What kind of brakes, did anyone come across?
I tried to work with the loaded configuration, add, edit information (as a user), everything works without brakes ...
But there is something terrible with saving the configuration. Or is that how it should be?

Answer 1

No, it's not normal. UNF conf should load quickly. I did not have such brakes on this configuration on a virtual server with Ubuntu. I don’t remember exactly, but the saving was clearly no longer than 10 minutes (perhaps even within 5 minutes - I haven’t been servicing their server for 3 years, I just forgot).
Thoughts out loud:
1) The disk is far from being an SSD and is generally on its last legs.
2) The disk is fine, but the system is in an infinite swap.
3) The server administrator has cut access to resources for 1C server processes (cgroup or the like).