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 19:27:49 GMT

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

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

There may be occasions where String columns in a database contain large amounts of unnecessary
trailing whitespace.  To alleviate the movement and processing of this whitespace, I am introducing
a DBDictionary property to optionally trim this trailing whitespace after retrieving a String
field from a ResultSet.  The default value for this new property (DBDictionary.trimStringColumns)
will be "false" to allow existing applications to continue executing as they have today. 
But, for those applications where the removal of this whitespace can provide a performance
benefit, this property can be set to "true" and then trim() will be called on the String result
before returning it to the Entity.
                
> 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