Date of First Response: 2010-06-06 22:49:40 project_key: SOA
Link: Added: This issue depends JBESB-3326
Updated in ESB codebase, will be in next merge.
More information needed to document this: Is all the work here related to reducing the number of database queries ? The following items where taken from JBESB-3306. Do they adequately cover the work done here? - cache classification scheme NEED MORE INFO - generate deleted EPR information once NEED MORE INFO - check retrieved service for bindings before querying for bindings. Retrieved services are checked for binding information before querying the database. IS THIS ACCURATE?
-cache classification schema The classification scheme was repeatedly queried from the repository even though this information does not change, once retrieved it can be cached and reused. - generate deleted EPR information once The implementation has to discover the correct EPR to delete and, to achieve this, compares the current EPR string representation with those in the repository. The previous implementation generated the string representation of the deleted EPR for every comparison, rather than generating it once and then comparing with each EPR in the registry. - check retrieved service for bindings before querying for bindings The process to query current list of EPRs involves two steps, query for the service information and then search for associated bindings. The jUDDI v2 implementation returns the associated bindings as part of the overall service information and allows us to miss out the second, more intensive, juddi v2 query.
Added to the SOA 5.0.2 release notes as resolved: JBESB-3326 JAXRRegistryImpl has had the following performance enhancements. * Classification schemes are now cached when retrieved so they can be reused without having to query the database again. * When deleting End Point References (EPRs), the string representation of the EPR to delete is now only generated once and reused for each EPR comparision instead of re-creating it each time. * The process for querying the current list of EPRs now reuses the associated bindings information returned with the overall service information instead of performing a separate query for this information.
Verified in 5.0.2.GA
Performance results comparison attached
Attachment: Added: SOA-P-JUDDI-performance-comparison.ods