have you found out why? I have very similar config as yours: XP/JBoss 4.2.2/JDK5/Seam 2.1.1GA, localhost much slower than using Seam 2.0.1.
Try disabling Seam debug in components.xml
<core:init debug="false" ... >
I migrated our portal application from Seam 2.0 to Seam 2.1 and the performance seems much worse than before, although it was already bad with Seam 2.0.
My performance test walks through some of the application pages 50 times each. There is nothing special, just short lists of less than 10 elements and single element information pages.
With Seam 2.0 the average response is 140ms, with Seam 2.1 1500ms, ie. ten times more.
After disabling Seam debug, I am able to get 1000ms responses.
It seems that Seam 2.1 is slower all over the application not depending what the page is actually doing, for example, the signout is 8 times slower with Seam 2.1. The application is the same in both cases, except for the api changes and security rules cause by Seam 2.1 migration. There are the following version differences:
Seam 2.0 and JBoss Portal 2.6.6.GA
<properties> <seam>2.0.2.SP1</seam> <seam.version>2.0.2.SP1</seam.version> <portletbridge.version>1.0.0.B4</portletbridge.version> <jsf.version>1.2_07</jsf.version> <richfaces.version>3.2.2.GA</richfaces.version> </properties>
Seam 2.1 and JBoss Portal 2.7.2
<properties> <seam.version>2.1.1.GA</seam.version> <portletbridge.version>1.0.0.CR1</portletbridge.version> <jsf.version>1.2_12</jsf.version> <richfaces.version>3.3.0.GA</richfaces.version> </properties>
Is this to do with Seam version, JBoss portal version, JBoss Portletbridge version or something else? Any ideas? Is there something wrong with my tests? In each case I am running same JMeter test plan against the application deployed to localhost.