ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Boisvert (JIRA)" <j...@apache.org>
Subject [jira] Commented: (ODE-495) Implement ODE DAO directly by JDBC instead of JPA(OpenJPA) as a choice to improve performance dramaticly
Date Tue, 20 Jan 2009 22:43:02 GMT

    [ https://issues.apache.org/jira/browse/ODE-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665611#action_12665611

Alex Boisvert commented on ODE-495:

Yes, you can implement the Ode DAOs with plain JDBC, or a lighter framework than JPA or Hibernate.

Keep in mind, however, that in our testing the bottleneck was not the persistence framework,
it was the amount of information persisted (write bandwidth) in the database.  So even using
plain JDBC you will likely experience similar overall performance if you persist the same
amount of information.

> Implement ODE DAO directly by JDBC instead of JPA(OpenJPA) as a choice to improve performance
> --------------------------------------------------------------------------------------------------------
>                 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
> 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.

View raw message