[
https://issues.apache.org/jira/browse/ODE-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tammo van Lessen updated ODE-495:
---------------------------------
Fix Version/s: (was: 1.3.5)
1.4
> Implement ODE DAO directly by JDBC instead of JPA(OpenJPA) as a choice to
> improve performance dramaticly
> --------------------------------------------------------------------------------------------------------
>
> Key: ODE-495
> URL: https://issues.apache.org/jira/browse/ODE-495
> Project: ODE
> Issue Type: Improvement
> Components: BPEL Runtime
> Affects Versions: 1.2
> Environment: JAVA 5.0+
> Reporter: Shammy Chen
> Fix For: 1.4
>
>
> 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?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
