Geek Answers Handbook

MSDTC (Distributed Transaction Coordinator) slow startup for the first time

I noticed that very simple distributed transactions take enough time (3-4 seconds) to complete in the first run. But if you repeat the same transaction volume, it will be much faster (30 ms). It seems that MSDTC goes to bed after an hour. After an hour, the next transaction will take 3-4 seconds.

I do not expect a lot of traffic on the site, so probably many hours can elapse between individual transactions.

I thought this was possible because the MSDTC service was started manually, but I made sure that the MSDTC services were working automatically.

Guess the registry setting there, but I was not lucky to find anything on MSDN.

Thanks!

+4
source share
2 answers

MSDTC launches COM components for transaction processing, and after 20 minutes (in my opinion, by default) the components are unloaded from memory. The slowdown that you observe in the first transaction is an environment that rotates and loads things into memory.

+2
source

Today I came across this question, and I know that the question is old, but I studied similar and came across this:

http://support.microsoft.com/kb/197810

This KB is also old, but it seems to me that there is something around closed unoccupied connections. It also lists registry settings. I'm not sure if this helps, but my scenarios are completely different, so this is not a problem (if it really is), I just wanted to know what was going on.

I'm not quite sure that MSDTC works as a component of COM +. There is a COM interface for this, but I could not find anywhere mentioning that it is a component of COM +. It is listed as a service, and the COM interface can be bypassed so that MSDTC can access directly. With all of this, I really doubt that it is a COM + component. Having said that, it has several other dependencies - like, for example, an RPC carter, they can also be involved in this problem.

+1
source

More articles:


All Articles