Why is no performance improvement observed when the Number of ORB Threads is increased, while using the TIBCO Adapter(TM) for CORBA with Orbix 6?
Article ID: KB0088278
Updated On:
| Products | Versions |
|---|---|
| TIBCO Adapter for CORBA | - |
| Not Applicable | - |
Description
Resolution:
Description:
==========
The 'Number of ORB Threads' is increased in the TIBCO Adapter(TM) for CORBA (CORBA Adapter) for Orbix 6. This does not result in faster processing of the messages. i.e. 'Number of ORB Threads' 1, 5, or 10 would yield the same throughput.
Environment:
===========
Orbix 6 for C++
Resolution:
==========
In the Orbix 6 ORB, the thread pool is managed by a Work queue. The default ORB will create an AutomaticWorkQueue.
According to the Orbix 6 documentation (CORBA Programmer's Guide, C++ -> Managing Server Objects-> Work Queues -> AutomaticWorkQueue), "An AutomaticWorkQueue is a work queue that feeds a thread pool. Automatic work queues process requests in the same way that the standard ORB does; however, it does allow the developer to assign a customized thread pool to a particular POA. Also, the developer can implement several automatic work queues to process different types of requests at different priorities.".
This implies that the Automatic Work Queue will create the threads as required by default, generally depending on the number of messages.
CORBA Adapter v5.4.0 does not create a work queue. The Orbix6 ORB will create a work queue with the default values. Kindly note that the "Number of ORB Threads" in the adapter configuration indicates the number of threads created as the adapter initializes. After the adapter initialization, the number of threads are created/destroyed by the Automatic Work Queue.
Therefore, increasing the number of ORB threads does not contribute towards better performance of the CORBA adapter when Orbix 6 is being used as the ORB.
Description:
==========
The 'Number of ORB Threads' is increased in the TIBCO Adapter(TM) for CORBA (CORBA Adapter) for Orbix 6. This does not result in faster processing of the messages. i.e. 'Number of ORB Threads' 1, 5, or 10 would yield the same throughput.
Environment:
===========
Orbix 6 for C++
Resolution:
==========
In the Orbix 6 ORB, the thread pool is managed by a Work queue. The default ORB will create an AutomaticWorkQueue.
According to the Orbix 6 documentation (CORBA Programmer's Guide, C++ -> Managing Server Objects-> Work Queues -> AutomaticWorkQueue), "An AutomaticWorkQueue is a work queue that feeds a thread pool. Automatic work queues process requests in the same way that the standard ORB does; however, it does allow the developer to assign a customized thread pool to a particular POA. Also, the developer can implement several automatic work queues to process different types of requests at different priorities.".
This implies that the Automatic Work Queue will create the threads as required by default, generally depending on the number of messages.
CORBA Adapter v5.4.0 does not create a work queue. The Orbix6 ORB will create a work queue with the default values. Kindly note that the "Number of ORB Threads" in the adapter configuration indicates the number of threads created as the adapter initializes. After the adapter initialization, the number of threads are created/destroyed by the Automatic Work Queue.
Therefore, increasing the number of ORB threads does not contribute towards better performance of the CORBA adapter when Orbix 6 is being used as the ORB.
Issue/Introduction
Why is no performance improvement observed when the Number of ORB Threads is increased, while using the TIBCO Adapter(TM) for CORBA with Orbix 6?
Feedback
Yes
No
Powered by
