[ODE-495] Implement ODE DAO directly by JDBC instead of JPA(OpenJPA) as a choice to improve performance dramaticly

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.2
• Fix Version/s: 1.4
• Component/s: BPEL Runtime
• Environment: JAVA 5.0+
• Assignee: Unassigned
• Reporter: Shammy Chen
• Created: 20/Jan/09 09:49
• Updated: 25/Nov/10 13:19

Description

Recently I've been testing ODE and tempo(modified) thoroughly, but it performed not too good, actually our customers even refuse to use it since their trades greatly exceed ODE's throughput. I am trying to make it perform better, and I tried many ways, filter ODE enevts,increase ODE-Server threads, increase database connections, increase integration layer threads, still it performs under our(customer's) expectation.

Then I tried to use memdao to see what makes ODE slow down, I found memdao run at least 7~8 times faster than jpadao.So I deduce that database operation is critical to performance.We have two ways to solve this problem, do less database operations or make the operation faster(or both).Then I did a comparision between OpenJPA and JDBC,and I found JDBC perform almost ten times better than OpenJPA . Our clients don't care how we implement the system at all,what they really care is how good the system fulfills their business goals,what they really care is the system's stability and performance.Can we implement ODE DAO by JDBC to improve performance?