VBJ 6.0: Performance issues with VisiNaming service

Problem:

• Product Name: VisiBroker
• Product Version: 6.0
• Product Component: Naming Service
• Platform/OS Version: All

VBJ 6.0: Performance issues with VisiNaming service.

For Naming Service that makes use database (especially with Sybase) as the back-end persistent store, time taken for a resolve operation could take lots of time depending on how far the database is from the server, OS used, etc.. Any ways to improve the performance of resolve call?

Resolution:

The performance can be improved by using the caching mechanism where the server objects once retrieved from the database can be cached and hence, a call to the database is not necessary for every resolve call.

The properties used for that would be

vbroker.naming.cacheOn=1
vbroker.naming.cacheSize=5

A scenario when caching will not work is when to bind a context to a naming service with bind() call. Instead, bind_context() call should be used.

Author: Meghana Rao