You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Jeremy Bauer (Created) (JIRA)" <ji...@apache.org> on 2012/02/24 20:33:48 UTC
[jira] [Created] (OPENJPA-2143) Reduce lock contention on
LifeCycleEventManager
Reduce lock contention on LifeCycleEventManager
-----------------------------------------------
Key: OPENJPA-2143
URL: https://issues.apache.org/jira/browse/OPENJPA-2143
Project: OpenJPA
Issue Type: Improvement
Components: kernel
Affects Versions: 2.3.0, 2.2.1
Reporter: Jeremy Bauer
Assignee: Jeremy Bauer
Profiles have shown the synchronization pattern used on LifecycleEventManager diversely affects performance on multi-core systems. I'll be providing a fix that has shown to reduce lock contention on this class.
--
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-2143) Reduce lock contention on
LifecycleEventManager
Posted by "Jeremy Bauer (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Bauer updated OPENJPA-2143:
----------------------------------
Summary: Reduce lock contention on LifecycleEventManager (was: Reduce lock contention on LifeCycleEventManager)
> Reduce lock contention on LifecycleEventManager
> -----------------------------------------------
>
> Key: OPENJPA-2143
> URL: https://issues.apache.org/jira/browse/OPENJPA-2143
> Project: OpenJPA
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 2.3.0, 2.2.1
> Reporter: Jeremy Bauer
> Assignee: Jeremy Bauer
>
> Profiles have shown the synchronization pattern used on LifecycleEventManager diversely affects performance on multi-core systems. I'll be providing a fix that has shown to reduce lock contention on this class.
--
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-2143) Reduce lock contention on
LifecycleEventManager
Posted by "Jeremy Bauer (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Bauer resolved OPENJPA-2143.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.2.1
2.3.0
> Reduce lock contention on LifecycleEventManager
> -----------------------------------------------
>
> Key: OPENJPA-2143
> URL: https://issues.apache.org/jira/browse/OPENJPA-2143
> Project: OpenJPA
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 2.3.0, 2.2.1
> Reporter: Jeremy Bauer
> Assignee: Jeremy Bauer
> Fix For: 2.3.0, 2.2.1
>
>
> Profiles have shown the synchronization pattern used on LifecycleEventManager diversely affects performance on multi-core systems. I'll be providing a fix that has shown to reduce lock contention on this class.
--
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] [Reopened] (OPENJPA-2143) Reduce lock contention on
LifecycleEventManager
Posted by "Jeremy Bauer (Reopened) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Bauer reopened OPENJPA-2143:
-----------------------------------
New benchmarks have shown these changes to cause lock contention. Reopening to revert changes.
> Reduce lock contention on LifecycleEventManager
> -----------------------------------------------
>
> Key: OPENJPA-2143
> URL: https://issues.apache.org/jira/browse/OPENJPA-2143
> Project: OpenJPA
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 2.3.0, 2.2.1
> Reporter: Jeremy Bauer
> Assignee: Jeremy Bauer
> Fix For: 2.3.0, 2.2.1
>
>
> Profiles have shown the synchronization pattern used on LifecycleEventManager diversely affects performance on multi-core systems. I'll be providing a fix that has shown to reduce lock contention on this class.
--
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-2143) Reduce lock contention on
LifecycleEventManager
Posted by "Jeremy Bauer (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Bauer closed OPENJPA-2143.
---------------------------------
> Reduce lock contention on LifecycleEventManager
> -----------------------------------------------
>
> Key: OPENJPA-2143
> URL: https://issues.apache.org/jira/browse/OPENJPA-2143
> Project: OpenJPA
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 2.3.0, 2.2.1
> Reporter: Jeremy Bauer
> Assignee: Jeremy Bauer
> Fix For: 2.3.0, 2.2.1
>
>
> Profiles have shown the synchronization pattern used on LifecycleEventManager diversely affects performance on multi-core systems. I'll be providing a fix that has shown to reduce lock contention on this class.
--
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-2143) Reduce lock contention on
LifecycleEventManager
Posted by "Jeremy Bauer (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Bauer resolved OPENJPA-2143.
-----------------------------------
Resolution: Fixed
Reverted back to previous code in 2.2.x and trunk.
> Reduce lock contention on LifecycleEventManager
> -----------------------------------------------
>
> Key: OPENJPA-2143
> URL: https://issues.apache.org/jira/browse/OPENJPA-2143
> Project: OpenJPA
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 2.3.0, 2.2.1
> Reporter: Jeremy Bauer
> Assignee: Jeremy Bauer
> Fix For: 2.3.0, 2.2.1
>
>
> Profiles have shown the synchronization pattern used on LifecycleEventManager diversely affects performance on multi-core systems. I'll be providing a fix that has shown to reduce lock contention on this class.
--
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-2143) Reduce lock contention on
LifecycleEventManager
Posted by "Jeremy Bauer (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Bauer closed OPENJPA-2143.
---------------------------------
> Reduce lock contention on LifecycleEventManager
> -----------------------------------------------
>
> Key: OPENJPA-2143
> URL: https://issues.apache.org/jira/browse/OPENJPA-2143
> Project: OpenJPA
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 2.3.0, 2.2.1
> Reporter: Jeremy Bauer
> Assignee: Jeremy Bauer
> Fix For: 2.3.0, 2.2.1
>
>
> Profiles have shown the synchronization pattern used on LifecycleEventManager diversely affects performance on multi-core systems. I'll be providing a fix that has shown to reduce lock contention on this class.
--
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