You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <de...@db.apache.org> on 2006/10/12 10:24:36 UTC

[jira] Created: (DERBY-1957) Factor out run-time statistics information from language ResultSet classes

Factor out run-time statistics information from language ResultSet classes
--------------------------------------------------------------------------

                 Key: DERBY-1957
                 URL: http://issues.apache.org/jira/browse/DERBY-1957
             Project: Derby
          Issue Type: Improvement
          Components: Performance, SQL
            Reporter: Knut Anders Hatlen
            Priority: Minor


The discussion in DERBY-1876 indicated that the performance of simple queries could be improved by factoring out run-time statistics information from the language ResultSet classes.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (DERBY-1957) Factor out run-time statistics information from language ResultSet classes

Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dag H. Wanvik updated DERBY-1957:
---------------------------------

    Derby Categories: [Performance]

> Factor out run-time statistics information from language ResultSet classes
> --------------------------------------------------------------------------
>
>                 Key: DERBY-1957
>                 URL: https://issues.apache.org/jira/browse/DERBY-1957
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>
> The discussion in DERBY-1876 indicated that the performance of simple queries could be improved by factoring out run-time statistics information from the language ResultSet classes.

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


[jira] Commented: (DERBY-1957) Factor out run-time statistics information from language ResultSet classes

Posted by "Knut Anders Hatlen (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-1957?page=comments#action_12441664 ] 
            
Knut Anders Hatlen commented on DERBY-1957:
-------------------------------------------

Daniel John Debrunner wrote this in a comment to DERBY-1876:

> I've thought in the past about having the common statistic
> information in a language ResultSet implementation that could wrap
> the real langugae ResultSet. Then the ResultSetFactory would return
> a instance of the real ResultSet wrapped with a StatisticsResultSet
> when timing etc. was enabled. The StatisticsResultSet would have
> code like:
>
> class StatisticsResultSet {
>    private long openTime;
>
>    private final ResultSet rs;
>
>    pubic void openCore() {
>        long s = System.currentTimeMillis();
>        rs.openCore();
>        long e = System.currentTimeMillis();
>
>        openTime += (e -s);
>    }
>
> This then removes the common fields and code to get the times from
> all the ResultSet classes, also leading to consistency.
>
> The issue with this that code that performs instanceof checks to get
> specific behaviour of a ResultSet no longer works, though there are
> solutions to that:
>     A) Don't do it, it breaks the api in that the ResultSetFactory
>        says it is returning a ResultSet, so that's all the callers
>        should depend on.
>     B) Follow the JBDC wrapper model, have a getRealResultSet() call
>        in ResultSet api which would return this for most
>        implementations, but the wrapped rs for
>        StatisticsResultSet. Then code that needed to access the
>        specific class would use the return from that method.

> Factor out run-time statistics information from language ResultSet classes
> --------------------------------------------------------------------------
>
>                 Key: DERBY-1957
>                 URL: http://issues.apache.org/jira/browse/DERBY-1957
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL, Performance
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>
> The discussion in DERBY-1876 indicated that the performance of simple queries could be improved by factoring out run-time statistics information from the language ResultSet classes.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Closed: (DERBY-1957) Factor out run-time statistics information from language ResultSet classes

Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Knut Anders Hatlen closed DERBY-1957.
-------------------------------------

    Resolution: Won't Fix

After DERBY-827, the performance benefit of fixing this issue is negligible, so I'm closing it as "Won't Fix".

> Factor out run-time statistics information from language ResultSet classes
> --------------------------------------------------------------------------
>
>                 Key: DERBY-1957
>                 URL: https://issues.apache.org/jira/browse/DERBY-1957
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>
> The discussion in DERBY-1876 indicated that the performance of simple queries could be improved by factoring out run-time statistics information from the language ResultSet classes.

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