|<< Back to previous view|
[GLASSFISH-18272] [perf] Excessive lock contention during execution of trade2 in-memory replication benchmark with JRockit VM Created: 30/Jan/12 Updated: 03/Dec/12 Resolved: 31/Jan/12
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Participants:||amitagarwal and Mahesh Kannan|
Trade2 in-memory replication benchmark with JRockit VM gives 90% lower throughput than Sun Hotspot VM. Thread dump shows contention in following code-path,
"http-thread-pool-8080(4)" id=142 idx=0x220 tid=32438 prio=5 alive, blocked, native_blocked, daemon
|Comment by amitagarwal [ 30/Jan/12 06:25 PM ]|
Tried a patch provided by Scott, this resolves the contention and throughput improved significantly (from 800 ops/sec to over 8000 ops/sec).
|Comment by Mahesh Kannan [ 31/Jan/12 07:39 AM ]|
svn commit -m "Fix for 18272. Tested by Amit. Reviewed by Marina. QL & EJB devtests passed"
Approved by: Joe Di Pol
What is the impact on the customer of the bug?
What is the cost/risk of fixing the bug?
Is there an impact on documentation or message strings?
Which tests should QA (re)run to verify the fix did not destabilize GlassFish?
Which is the targeted build of 3.1.2 for this fix?