You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Rick Curtis (JIRA)" <ji...@apache.org> on 2009/12/08 19:46:18 UTC
[jira] Created: (OPENJPA-1421) Reduce lock contention in
JDBCStoreManager
Reduce lock contention in JDBCStoreManager
------------------------------------------
Key: OPENJPA-1421
URL: https://issues.apache.org/jira/browse/OPENJPA-1421
Project: OpenJPA
Issue Type: Bug
Components: kernel
Affects Versions: 1.2.2, 1.3.0
Reporter: Rick Curtis
Assignee: Rick Curtis
Fix For: 1.2.2, 1.3.0
When testing on a high end machine, we found a bottleneck in calling JDBCStoreManager.getCacheMapFromQuerySQLCache(...). To fix the problem, had each caller will hold onto the cacheMap that is returned from getCacheMapFromQuerySQLCache(...) rather than call it multiple times.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (OPENJPA-1421) Reduce lock contention in
JDBCStoreManager
Posted by "Rick Curtis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Curtis closed OPENJPA-1421.
--------------------------------
Resolution: Fixed
Committed changes to 1.2.x and 1.3.x. This problem does not exist on trunk.
> Reduce lock contention in JDBCStoreManager
> ------------------------------------------
>
> Key: OPENJPA-1421
> URL: https://issues.apache.org/jira/browse/OPENJPA-1421
> Project: OpenJPA
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.2.2, 1.3.0
> Reporter: Rick Curtis
> Assignee: Rick Curtis
> Fix For: 1.2.2, 1.3.0
>
>
> When testing on a high end machine, we found a bottleneck in calling JDBCStoreManager.getCacheMapFromQuerySQLCache(...). To fix the problem, had each caller will hold onto the cacheMap that is returned from getCacheMapFromQuerySQLCache(...) rather than call it multiple times.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OPENJPA-1421) Reduce lock contention in
JDBCStoreManager
Posted by "Rick Curtis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788730#action_12788730 ]
Rick Curtis commented on OPENJPA-1421:
--------------------------------------
>trunk should not have this method at all.
Correct.
> Reduce lock contention in JDBCStoreManager
> ------------------------------------------
>
> Key: OPENJPA-1421
> URL: https://issues.apache.org/jira/browse/OPENJPA-1421
> Project: OpenJPA
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.2.2, 1.3.0
> Reporter: Rick Curtis
> Assignee: Rick Curtis
> Fix For: 1.2.2, 1.3.0
>
>
> When testing on a high end machine, we found a bottleneck in calling JDBCStoreManager.getCacheMapFromQuerySQLCache(...). To fix the problem, had each caller will hold onto the cacheMap that is returned from getCacheMapFromQuerySQLCache(...) rather than call it multiple times.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OPENJPA-1421) Reduce lock contention in
JDBCStoreManager
Posted by "Pinaki Poddar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788187#action_12788187 ]
Pinaki Poddar commented on OPENJPA-1421:
----------------------------------------
> This problem does not exist on trunk.
trunk should not have this method at all.
> Reduce lock contention in JDBCStoreManager
> ------------------------------------------
>
> Key: OPENJPA-1421
> URL: https://issues.apache.org/jira/browse/OPENJPA-1421
> Project: OpenJPA
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.2.2, 1.3.0
> Reporter: Rick Curtis
> Assignee: Rick Curtis
> Fix For: 1.2.2, 1.3.0
>
>
> When testing on a high end machine, we found a bottleneck in calling JDBCStoreManager.getCacheMapFromQuerySQLCache(...). To fix the problem, had each caller will hold onto the cacheMap that is returned from getCacheMapFromQuerySQLCache(...) rather than call it multiple times.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.