You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2009/12/09 04:16:18 UTC
[jira] Updated: (TAP5-945) Unnecessary and severe lock contention
in PerthreadManagerImpl
[ https://issues.apache.org/jira/browse/TAP5-945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-945:
--------------------------------------
Summary: Unnecessary and severe lock contention in PerthreadManagerImpl (was: Lock contention in PerthreadManagerImpl)
> Unnecessary and severe lock contention in PerthreadManagerImpl
> --------------------------------------------------------------
>
> Key: TAP5-945
> URL: https://issues.apache.org/jira/browse/TAP5-945
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.1.0.5
> Reporter: Olle Hallin
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> When load testing our new high-volume site before soft launch, we found that we have severe lock contention in org.apache.tapestry5.ioc.internal.services.PerthreadManagerImpl.
> It synchronizes on "this" before invoking ThreadLocal.get() and ThreadLocal.remove(), which I believe is unnecessary.
> During our tests, approximately 35% of all Tomcat threads were waiting for this lock in any of 10 thread dumps taken 15 seconds apart.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.