[JBoss-dev] [ jboss-Bugs-658042 ] High contention in jboss/naming
Bugs item #658042, was opened at 2002-12-23 15:42 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=658042group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Stefan Reich (sreich) Assigned to: Nobody/Anonymous (nobody) Summary: High contention in jboss/naming Initial Comment: While running ECperf Scott and I discovered high contention in two classes of the JNDI naming implementation of JBoss: 1) org.jboss.naming.ENCFactory calls a native method (Thread.currentThread) while holding a lock, which is very expensive in most vms. Fix: moved the call out of the synchronized bloc. 2) org.jnp.interfaces.NamingParser has a static Properties instance that holds JNDI read-only properties. In the tests we saw as many as 30% of all threads waiting to acquire the lock for the Hashtable, from which java.util.Properties extends. The synchronization is unnecessary, since the static instance is read-only after its allocation. Fix: wrote a custom class that extends java.util.Properties overriding all methods to get rid of unwanted locking and ensure read-only semantics. Both fixes result in an increase of about factor three in ECperf BBops on a Dual 500MHz PowerMac and have been tested for a week on Jboss 3.0.5RC1. Diff attached. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=658042group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-658042 ] High contention in jboss/naming
Bugs item #658042, was opened at 2002-12-23 15:42 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=658042group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Closed Resolution: Fixed Priority: 5 Submitted By: Stefan Reich (sreich) Assigned to: Scott M Stark (starksm) Summary: High contention in jboss/naming Initial Comment: While running ECperf Scott and I discovered high contention in two classes of the JNDI naming implementation of JBoss: 1) org.jboss.naming.ENCFactory calls a native method (Thread.currentThread) while holding a lock, which is very expensive in most vms. Fix: moved the call out of the synchronized bloc. 2) org.jnp.interfaces.NamingParser has a static Properties instance that holds JNDI read-only properties. In the tests we saw as many as 30% of all threads waiting to acquire the lock for the Hashtable, from which java.util.Properties extends. The synchronization is unnecessary, since the static instance is read-only after its allocation. Fix: wrote a custom class that extends java.util.Properties overriding all methods to get rid of unwanted locking and ensure read-only semantics. Both fixes result in an increase of about factor three in ECperf BBops on a Dual 500MHz PowerMac and have been tested for a week on Jboss 3.0.5RC1. Diff attached. -- Comment By: Scott M Stark (starksm) Date: 2002-12-23 17:07 Message: Logged In: YES user_id=175228 Integrated into 3.0+ -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=658042group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
