You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Kevin Sutter (Created) (JIRA)" <ji...@apache.org> on 2012/02/08 20:29:00 UTC
[jira] [Created] (OPENJPA-2123) Minor performance improvements for
Connection and ResultSet processing
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
Reporter: Kevin Sutter
Assignee: Kevin Sutter
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
[jira] [Closed] (OPENJPA-2123) Minor performance improvements for
Connection and ResultSet processing
Posted by "Albert Lee (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Albert Lee closed OPENJPA-2123.
-------------------------------
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OPENJPA-2123) Minor performance improvements
for Connection and ResultSet processing
Posted by "Kevin Sutter (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (OPENJPA-2123) Minor performance improvements for
Connection and ResultSet processing
Posted by "Kevin Sutter (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Sutter updated OPENJPA-2123:
----------------------------------
Affects Version/s: 2.2.1
Fix Version/s: 2.2.1
2.3.0
> 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
[jira] [Resolved] (OPENJPA-2123) Minor performance improvements for
Connection and ResultSet processing
Posted by "Albert Lee (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Albert Lee resolved OPENJPA-2123.
---------------------------------
Resolution: Fixed
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OPENJPA-2123) Minor performance improvements
for Connection and ResultSet processing
Posted by "Kevin Sutter (Commented) (JIRA)" <ji...@apache.org>.
[ 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