Problem: Product: VisiBroker Version: All Platform: All Product component: Naming Service. A round trip time in excess of 3 minutes when rebinding with the Naming Service is experienced. Is there any properties that can be used to improve the performance? Resolution: It is possible that the number of threads are growing because the number of threads is not limited. Please confirm that the maxThreads and threadMaxIdle time are the default values. The default values may not really optimal for high load. The Naming Service will allocate one thread/connection for each incoming client and will keep them open until the client process dies. For performance, you can tune these parameters until the optimal performance is reached (specially decreasing the number of allowed threads/connections). vbroker.se.iiop_tp.scm.iiop_tp.dispatcher.threadMaxIdle vbroker.se.iiop_tp.scm.iiop_tp.dispatcher.threadMin vbroker.se.iiop_tp.scm.iiop_tp.dispatcher.threadMax vbroker.se.iiop_tp.scm.iiop_tp.manager.connectionMaxIdle vbroker.se.iiop_tp.scm.iiop_tp.manager.connectionMax The garbage collector is not (should not be) the initiator of thread removal process. The threading management is done internally in VB, and this is configurable. Because there is no limitation for the number of threads/connections, the process' memory size can grow indefinitely. Setting Java VM's heap size can be helpful. Beside tuning the Naming Service, the database response time can be increased by adding some table indexes if a database is used as a backing store. For a more detailed information about performance tuning in VisiBroker, please refer to this article: VisiBroker Performance Tuning
↧