>Rick Strahl is the guy to talk to here, as he has tested it.

Agreed. I hope he joins this discussion...

>One understanding I have is that with MTS there is no way to limit the amount of threads that start... MTS will just merrily keep adding threads rather than Queue them up... however, I think COM+ was supposed to deal with that.
>

As I understand it, the pooling mechanism was not in MTS 2.0. And, I don't think it is going to be in COM+ Services either...


>1. Is instantiation... Ricks pool manager keeps the com object avilable at all times... where MTS shuts them down... now, granted MTS keeps some stuff cached... If you have hits that are close enough togther this is not an issue, but if they are less frequent there is a startup time with MTS.
>

You timeout period is configurable. However, when you have to wait for a COM Component to fire up in MTS, it is a bit of a wait...


>2. Is the overhead of MTS... MTS is an Out-of-Process server that hosts in-process server, and there is an overhead you pay for with MTS... so, if you are not using the role based security of transaction features you are still paying for them.
>

Well, if you have a gig or so of RAM, is this really a big deal??? I don't think so...