Yes when run under load (25 users) the system seems to becomes unresponsive. The requests do eventually return - jmeter was reporting an average request time of 100+ seconds. When accessed during the warm up requests (my manual requests to prime the application) the application functioned just fine.<br>
<br>-Jay<br><br><div class="gmail_quote">On Wed, Nov 12, 2008 at 8:20 PM, Shane Bryzak <span dir="ltr"><<a href="mailto:shane.bryzak@jboss.com">shane.bryzak@jboss.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Thanks Jay,<br>
<br>
Just to be clear, did you mean that each individual request is now taking 100+ seconds as compared to 3 seconds previously?<br>
<br>
Jay Balunas wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">
Performance Review of current Seam trunk fo 2.1.1<br>
--------------------------------------------------------<br>
<br></div>
Working with the latest trunk from today (r9557) and testing the performance changes that were made. Previous tests were done with (r9017). Just as a refresher my baseline test uses the wiki example with all of the <a href="http://sfwk.org" target="_blank">sfwk.org</a> <<a href="http://sfwk.org" target="_blank">http://sfwk.org</a>> data up to July 31st 2008. <div class="Ih2E3d">
<br>
For these tests I use JBoss AS 4.2.3 with JDK5 on my linux machine. Jmeter is used to load test and calculate the results and graphs. I then use JProfiler to to identify either blocking threads, call graphs, and CPU usage. <br>
Unfortunately the results were not good. I was using a mixture of 25 and 50 users - hitting the server 25 times each. As before they were accessing the first page of the user forum.<br>
<br>
With r9017 the 25 user x 25 requests averaged 3 seconds a request. With trunk they were 100+ seconds. Thinking something was wrong with the system I replaced the 9557 wiki.war with the 9017 and reran with all other variables the same. Again the 9017 saw about 3 seconds for the average over the 625 requests.<br>
<br>
I then profiled the server under load as I did before. The methods below appear to be the primary offenders although as with most blocking threads there are some others waiting on the same monitor. I'll follow up this email with the stack traces, and more information from my investigation.<br>
<br>
-----------------------------------<br>
1) com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate.findLock(..)<br>
- This appears to be the biggest issue. Every requests are generating many of these calls.<br>
- <a href="http://viewvc.jboss.org/cgi-bin/viewvc.cgi/labs/labs/jbosstm/branches/JBOSSTS_4_2_3_GA_SP/atsintegration/classes/com/arjuna/ats/jbossatx/jta/TransactionManagerDelegate.java?view=markup" target="_blank">http://viewvc.jboss.org/cgi-bin/viewvc.cgi/labs/labs/jbosstm/branches/JBOSSTS_4_2_3_GA_SP/atsintegration/classes/com/arjuna/ats/jbossatx/jta/TransactionManagerDelegate.java?view=markup</a><br>
- It looks like every interaction with any transaction causing synchronization issues with this call.<br>
- We'll need to find a way to limit these calls.<br>
- I'm guessing some of the changes made for JBSEAM-3519 may be the cause although I have not had time to look deeper.<br></div>
- See : <a href="http://fisheye.jboss.org/browse/Seam/trunk/src/main/org/jboss/seam/transaction/TransactionInterceptor.java?r1=8626&r2=9552&u=-1&ignore=&k=" target="_blank">http://fisheye.jboss.org/browse/Seam/trunk/src/main/org/jboss/seam/transaction/TransactionInterceptor.java?r1=8626&r2=9552&u=-1&ignore=&k=</a> <<a href="http://fisheye.jboss.org/browse/Seam/trunk/src/main/org/jboss/seam/transaction/TransactionInterceptor.java?r1=8626&r2=9552&u=-1&ignore=&k=" target="_blank">http://fisheye.jboss.org/browse/Seam/trunk/src/main/org/jboss/seam/transaction/TransactionInterceptor.java?r1=8626&r2=9552&u=-1&ignore=&k=</a>><br>
<a href="http://fisheye.jboss.org/browse/Seam/trunk/src/main/org/jboss/seam/util/Work.java?r1=9221&r2=9550&u=-1&ignore=&k=" target="_blank">http://fisheye.jboss.org/browse/Seam/trunk/src/main/org/jboss/seam/util/Work.java?r1=9221&r2=9550&u=-1&ignore=&k=</a> <<a href="http://fisheye.jboss.org/browse/Seam/trunk/src/main/org/jboss/seam/util/Work.java?r1=9221&r2=9550&u=-1&ignore=&k=" target="_blank">http://fisheye.jboss.org/browse/Seam/trunk/src/main/org/jboss/seam/util/Work.java?r1=9221&r2=9550&u=-1&ignore=&k=</a>><div class="Ih2E3d">
<br>
-----------------------------------<br>
2) org.jboss.naming.ENCFactory.getObjectInstance()<br>
javax.naming.Context.lookup(java.lang.String)<br>
<br>
This appears to be the second biggest offender and it looks like we are no longer blocking on retrieving the InitialContext, but now blocking on performing the lookups using the context.<br>
-----------------------------------<br>
3) org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection()<br>
org.jboss.resource.connectionmanager.CachedConnectionManager.registerConnection()<br>
<br>
This is the third biggest issue, but much less than the others. 1 or 2 dozen blocks on 60 requests. These are all related to hibernate calls and database access from what I've seen so far.<br>
-----------------------------------<br>
I'll follow up this email tomorrow with the typical stack traces seen for each of these.<br>
<br>
Shane could you review, and I'll get more information on these tomorrow. <br>
Thanks,<br>
-Jay<br>
<br>
-- <br>
blog: <a href="http://in.relation.to/Bloggers/Jay" target="_blank">http://in.relation.to/Bloggers/Jay</a><br></div>
------------------------------------------------------------------------<br>
<br>
_______________________________________________<br>
seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org" target="_blank">seam-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
<br>
</blockquote>
<br>
</blockquote></div><br><br clear="all"><br>-- <br>blog: <a href="http://in.relation.to/Bloggers/Jay">http://in.relation.to/Bloggers/Jay</a><br>