-
1. Re: stress test: results are far from satisfying
mmaia Sep 30, 2010 12:21 PM (in response to walidkarray)Have you monitored cpu usage and idle time in both sides? I mean in the server side and also in the client machine running JMeter as I have already been in a scenario where client was overloaded by jmeter pretty much before the server I was trying to stress. If you notice this is the case you will need to use more client machines to run your tests.
regards.
-
2. Re: stress test: results are far from satisfying
walidkarray Oct 5, 2010 6:09 AM (in response to walidkarray)Thanks Marcos for your fast reply,
We have optimized throughput average to 20/s by removing three unused components:("drools, jbpm and mail") in "components.xml" but this average still inadequate for a "non business processing" call.
For the monitoring we did it by installing "Munin" both in client and server side to graph performances during the load test. Results are detailed below:
- Server side:
Load average=0.75
cpu= 10%
mem= 60% used
swap= 0%
- Client side:
load average=0.60
cpu= 16%
mem= 40% used
swap= 0%
=> You can easily note that both client and server are lightly loaded !
I have already made another different load test "http://seamframework.org/Community/AnWeRelyOnJBossSeamToSupportHeavyLoadCalls" and I discovered that's the long-time response comes from seam core components.
My best regards. -
3. Re: stress test: results are far from satisfying
lvdberg Oct 5, 2010 6:44 AM (in response to walidkarray)Hi,
see the answer in your other thread. You can't compare if you're not using a realistic scenario. For every
Seam enabled
tiny page, you indeed have a lot of overhead. But his is not very realistic. We seldom have applications containing only empty pages.Leo
-
4. Re: stress test: results are far from satisfying
yahawari Oct 6, 2010 6:56 PM (in response to walidkarray)if i am not mistaken, seam creates a transaction that wraps every request. to have an exact similar scenario, your two pages (jsf and jsf/seam)should get a couple of db records and display them.
u need to run seam in production mode as well (debug off).