Hi reamon and dhimate,
Thanks for your responses…
@ reamon:
It’s been my experience that caching config files isn’t valuable. It normally isn’t a bottleneck and caching it doesn’t speed things up meaningfully.
In my project, I need the config file to load for every incoming message processing for comparing the message level data with the data from the config files. Therfore, there are production scenarios where approximely 1 million messages gets bridged in a day. Therefor it is tedious to read the config file every time for procesing the incoming message. Therefore I have cached the service level data which loads the config files and I am expecting better performance improvement by this implementation. pls let me know if you don’t find any usefulness by this implemenation
@dhimate:
We have seen issues in some of our implementations where caching of services have not made any significant contribution to the performance. Instead of using IS provided caching, building a custom cache mechanism is more efficient. Using system level hashtable is one of the ways to implement this.
I am using config files which are in XML fomat. These are not property files (name-value pairs). Caching using Hashtable is easier if there are name-values pairs in a single heirarchy. But, I am using complex config file structure where it is difficult to cache the values using the hashtable.
if you know any other methods, please let me know.
Thanks and Regards,
Shriraksha A N