You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Alex Boisvert (JIRA)" <ji...@apache.org> on 2008/12/03 01:12:46 UTC

[jira] Updated: (ODE-444) Improve performance of InstanceManagement (1.x branch)

     [ https://issues.apache.org/jira/browse/ODE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Boisvert updated ODE-444:
------------------------------

    Summary: Improve performance of InstanceManagement (1.x branch)  (was: Improve performance of InstanceManagement)

> Improve performance of InstanceManagement (1.x branch)
> ------------------------------------------------------
>
>                 Key: ODE-444
>                 URL: https://issues.apache.org/jira/browse/ODE-444
>             Project: ODE
>          Issue Type: Task
>          Components: Management Console
>    Affects Versions: 1.2
>            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.