You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pivot.apache.org by "Greg Brown (JIRA)" <ji...@apache.org> on 2010/08/28 01:04:55 UTC

[jira] Resolved: (PIVOT-617) Optimize performance of ResultList

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

Greg Brown resolved PIVOT-617.
------------------------------

    Resolution: Fixed

> Optimize performance of ResultList
> ----------------------------------
>
>                 Key: PIVOT-617
>                 URL: https://issues.apache.org/jira/browse/PIVOT-617
>             Project: Pivot
>          Issue Type: Improvement
>          Components: wtk
>            Reporter: Greg Brown
>            Assignee: Greg Brown
>             Fix For: 1.5.2, 2.0
>
>
> On at least one JDBC driver, returning a 10,000-row result set using ResultList typically takes 75-85s, whereas retrieving the same data using ResultSet takes only 10s. Optimize performance of ResultList so it is on par with direct ResultSet access.
> Note that this will constitute an API change and slight loss of functionality (ResultList's iterator will only support forward-scrolling iteration, whereas previously it had supported bi-directional iteration). However, the performance benefits for the common case (forward-scrolling) should far outweigh the loss.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.