Why does the operation hang in 1s?

Question

1C

Hello.
The question is this:
After transferring the databases from the file mode to MicrosoftSQL, when choosing some operations, 1s freezes for (5-10 minutes), everything worked without problems in the file mode.

Initial data:
A physical server, a VM (hyper-v) is raised on it and a 1c-enterprise is deployed
On the Raid1 system, on the Raid10 bases, the logs are placed on a separate ssd
Gigabit network (ping is small, packets are not lost)
2 bases no more than 1Gb each
Work happens through the thin client.

Where to dig in which direction? There is nothing in the logs.

Answer 1

We start debugging, there is a performance measurement there, we do the necessary operation, we analyze it, who thinks for a long time, we correct it.

Answer 2

After transferring databases from file mode to MicrosoftSQL, when choosing some operations, 1s freezes for (5-10 minutes), in file mode everything worked without problems.

it's like poking a finger into the sky, forget about Raid1 and other pieces of iron.
It is necessary to look at 1s, what kind of operation is hanging. Minimum Logbook.
Further deal with her.

Answer 3

If we take only the voiced prerequisites:
1) there was a file one and became a server one
2) brakes when searching and then displaying all links to documents under the contract,
then the idea arises that the problems are precisely in the client-server interaction, which were not previously within the file emulation noticeable. You need to look in more detail - whether the selection slows down (non-optimal query plans for the DBMS), or a little later the output of the received one (all sorts of conditional formats and handlers When ReceivingData on the form where a million calls to the server were inserted).

Answer 4

It is necessary to indicate: what exactly the configuration is in question; And about what kind of operations!
In general, as already described above, the problem is easy to observe using the Performance Meter;
This whole thing is complicated by the fact that the brakes can be caused by third-party processes such as: Scheduled task, Writing to the registration log, no rights to create a temporary file, no space on the server, incorrect cluster settings restart worker processes;
I would start anyway with a performance measurement