openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Sutter (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OPENJPA-2123) Minor performance improvements for Connection and ResultSet processing
Date Wed, 22 Feb 2012 17:25:48 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213773#comment-13213773
] 

Kevin Sutter commented on OPENJPA-2123:
---------------------------------------

Found another minor improvement that is indirectly related to Connection and ResultSet processing...
 Whenever setQueryTimeout is processed with the DB2Dictionary, we make a call to a private
method to determine the level or version of DB2 that we're talking with.  This method is expensive
due to the string manipulation that is performed.  Since we have already determine the level
of DB2 during the connectedConfiguration() initialization, we can be more efficient by just
checking the value of db2ServerType instead of calling isDB2ZOSV8xOrLater().
                
> Minor performance improvements for Connection and ResultSet processing
> ----------------------------------------------------------------------
>
>                 Key: OPENJPA-2123
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2123
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc, performance
>    Affects Versions: 2.3.0, 2.2.1
>            Reporter: Kevin Sutter
>            Assignee: Kevin Sutter
>             Fix For: 2.3.0, 2.2.1
>
>
> Came across a few items that could help with performance in certain scenarios.  I'll
document each one as I determine the proper resolution.  The first one is that we were preparing
the ability to print the SQL parameters even if no configuration properties were set requesting
that capability.  This resulted in String and StringBuffer operations that were extra overhead
on every interaction with the Connection.
> More to come...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message