Restriction on Components in an MTS package

[jashy]

Hi
Im creating the middle tier business components for a three tier client/server application. Its being developped in VB 6.
The middle tier is going to be hosted in MTS.

Is there any restriction on how many components can be hosted in a single MTS package? I have some 40/50 odd classes (each very small ones) to be hosted in the MTS in one single package. Can that have some negative impact on the MTS performance?

Thanks [sig][/sig]

 

[VB400]

To my knowledge, there is no limit on how many components can exist in an MTS package or if there is one then it is a large number.

More components doesn't automatically translate into worse performance -- it all depends on usage. The worst offender to performance is object instantiation. MTS 2.0 does NOT support Object Pooling and thus it remains a performance issue.

So if one of your objects requires the creation of 10 other objects to get all it needs and this one object is heavily used by your frontend app then performance will be compromised. I think you get the idea!

Tarek [sig][/sig]

 

[jashy]

I have all these classes exposing same kind of methods. Which all require a maximum of two very small classes (non-MTS) to instantiate. So I dont think that can be a problem for me.

Thanks anyway [sig][/sig]

 

[zallen]

First I agree with VB400.
Usually MTS packages run as server processes.The performance should not be influenced by number of components in a package but the object pooling,database connection pooling,stateless or stateful,etc.

i think you 'd better put business-associated components in a package because it is easy to manage and dispatch!


Hope you understand what i said!


Regards!
[sig][/sig]