|
Home > Archive > EAserver > November 2005 > EASERVER PERFOMANCE
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
EASERVER PERFOMANCE
|
|
| JOSE MIGUEL 2005-11-21, 11:24 am |
| Hello, i'm doing a load test to an application in EAS 5,0
WorkGroup Edition. The server has the following
configuration:
HTTP THREADS: 200
IIOP THREADS: 10
MAX THREADS: 260
The comonents are java CORBA and has the configuration:
Concurrency enabled
Poolong enabled
Stateless enabled
When i run the LoadTest, it creates 200 threads that execute
a Java CORBA component expose as a WS.
In the runtime monitor (HTTP stats) I see 200 Maximum
threads, that is ok, but the peak maximum sessions are 7.
Why don=b4t use all threads available in the pool, the
response times increases very much.
thanks
| |
| a Friend 2005-11-23, 7:24 am |
| Surely you component is very simple, Web service use XML to
process data and that generate much overhead, this statistic
sound wear, but to probe my hypothesis just do a little
change in the component, if you can try to put one sleep in
the component (0.2 seconds sound good), in this way you will
add more component contention and your statistic must change
dramatically.
Let me know the results
Regards
A Friend
> Hello, i'm doing a load test to an application in EAS 5,0
> WorkGroup Edition. The server has the following
> configuration:
> HTTP THREADS: 200
> IIOP THREADS: 10
> MAX THREADS: 260
> The comonents are java CORBA and has the configuration:
> Concurrency enabled
> Poolong enabled
> Stateless enabled
>
> When i run the LoadTest, it creates 200 threads that
> execute a Java CORBA component expose as a WS.
> In the runtime monitor (HTTP stats) I see 200 Maximum
> threads, that is ok, but the peak maximum sessions are 7.
> Why don=b4t use all threads available in the pool, the
> response times increases very much.
> thanks
| |
|
| Thanks.
The component process XML executes Stored Procedures and
response. I Think that it doesn`t need a sleep, but I'll
probe it..
then I'll let you know the results...
Any other ideas?
[color=darkred]
> Surely you component is very simple, Web service use XML
> to process data and that generate much overhead, this
> statistic sound wear, but to probe my hypothesis just do a
> little change in the component, if you can try to put one
> sleep in the component (0.2 seconds sound good), in this
> way you will add more component contention and your
> statistic must change dramatically.
>
> Let me know the results
>
> Regards
> A Friend
>
>
the[color=darkred]
|
|
|
|
|