Object Pooling and COM+ JIT Activation
COM+ JIT activation essentially strikes a compromise between greedy clients and greedy servers for the sake of getting optimal performance. Clients get to keep object references, while servers can more closely manage memory utilization.
You can refine this further by using COM+ Object Pooling. By pooling objects that are JIT activated, you can dedicate a certain amount of memory to hold a certain number of objects active in memory, ready for immediate reuse. This makes the most sense when objects are expensive to create, as in the case where they hold multiple resources.
Pooling JIT-activated objects in this manner, you can achieve the following benefits:
- Greatly accelerated object reactivation times.
- Reuse of any expensive resources the objects are holding.
- More precise governing of memory and resource use for the pooled objects.
- Retention of administrative flexibility so that your application can scale to use available resources and adapt to changing performance requirements.
Related topics
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for