[JUDDI-89] JDBC Datastore performance improvements

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.9rc4
• Fix Version/s: 3.1.5
• Environment: Oracle
• Assignee: Kurt T Stam
• Reporter: Rémi Flament
• Created: 12/Jul/06 23:13
• Updated: 05/Apr/13 06:30
• Resolved: 05/Apr/13 06:30

Description

Hi,

Please find a huge patch attached.

We have used Juddi with more than an hundred business services and we had some issues. This patch correct these issues :

• Juddi was very slow with more than 1000 business services.
• Oracle cannot handle more than 1000 elements in SQL "IN" request, so Juddi crashed when a business entity contained more than 1000 services.

For the "IN" problem we added a method in util/Config which gives the maximum element the db can handle in IN requests.

For the performance problem we had to rewrite a lot of the JDBC datastore. Basically the thing is to avoid to do too much sql requests by grouping them. As an example instead of the method fetchService() we use the method fetchServices(), etc.

Thanks to these corrections we had great performance improvement : the getbusinessdetail used to take more than 40 seconds on big business entity, now it takes about 6 seconds.

This patch applies to v0.9rc4.

Regards,

Rémi Flament.

Issue Links

• is duplicated by: JUDDI-146 Hitting Oracle In Clause Limit Error during Find request
• is related to: JUDDI-569 Performance Issue fetching service list
• relates to: JUDDI-569 Performance Issue fetching service list