[
https://issues.apache.org/jira/browse/ODE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Boisvert resolved ODE-444.
-------------------------------
Resolution: Fixed
Fixed in Ode 1.x branch
[EMAIL PROTECTED]:~/svn/ode/1.1$ svn commit -m "ODE-444 Improve performance of
InstanceManagement service"
Sending
axis2-war/src/test/java/org/apache/ode/axis2/management/InstanceManagementTest.java
Sending
bpel-api/src/main/java/org/apache/ode/bpel/pmapi/InstanceManagement.java
Sending
bpel-dao/src/main/java/org/apache/ode/bpel/dao/BpelDAOConnection.java
Sending
bpel-dao/src/main/java/org/apache/ode/bpel/dao/CorrelationSetDAO.java
Sending
bpel-runtime/src/main/java/org/apache/ode/bpel/engine/ProcessAndInstanceManagementImpl.java
Sending
bpel-runtime/src/main/java/org/apache/ode/bpel/memdao/BpelDAOConnectionImpl.java
Sending
bpel-runtime/src/test/java/org/apache/ode/bpel/runtime/ActivityRecoveryTest.java
Sending
dao-hibernate/src/main/java/org/apache/ode/daohib/bpel/BpelDAOConnectionImpl.java
Sending
dao-hibernate/src/main/java/org/apache/ode/daohib/bpel/hobj/HCorrelationSet.java
Sending
dao-jpa/src/main/java/org/apache/ode/dao/jpa/BPELDAOConnectionImpl.java
Sending
dao-jpa/src/main/java/org/apache/ode/dao/jpa/CorrelationSetDAOImpl.java
Sending
dao-jpa/src/main/java/org/apache/ode/dao/jpa/ProcessInstanceDAOImpl.java
Transmitting file data ............
Committed revision 722680.
> Improve performance of InstanceManagement
> -----------------------------------------
>
> Key: ODE-444
> URL: https://issues.apache.org/jira/browse/ODE-444
> Project: ODE
> Issue Type: Task
> Components: Management Console
> Reporter: Alex Boisvert
> Fix For: 1.3
>
>
> There are some performance issues with the current
> InstanceManagement.listXXXInstances() operations, notably:
> 1) listAllInstances() is quite dangerous -- it will run into
> OutOfMemoryException if you have lots of instances
> 2) listAllInstancesWithLimit() is better but suffers performance-wise because
> it attempts to load the instance summary data, the events, the scopes and
> properties of the matching instances. This result is too much database
> activity for the common case, moreover the current implementation is horrific
> because it actually performs 4 joins for each instance!
> So I'm introducing listInstancesSummary(String filter, String order, int
> limit) that only loads the instance summary and the properties in only 3
> joins (total, not per instance) to address these performance issues and
> making both listAllInstances() and listAllInstancesWithLimit() use this
> method under the cover.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
