Hi again Scott,
>similar to yours, in that the average response time for a request
>remained fairly consistent.
>remained fairly consistent.
Does this mean that the amount of time to get a response back from a request was the same in your test for 1 and mutliple transactions. I would of thought an a noisy channel there would have been some performance issue?
>The configuration of your Web server, servlet container and even
>server OS can impact your results. All 3 likely have a pool of
>threads and/or memory structures from which resources are allocated
>to service requests. If the pools are small, your SOAP requests will
>sit in the queue longer. Making sure the pools are large enough is
>essential to obtain proper throughput.
>server OS can impact your results. All 3 likely have a pool of
>threads and/or memory structures from which resources are allocated
>to service requests. If the pools are small, your SOAP requests will
>sit in the queue longer. Making sure the pools are large enough is
>essential to obtain proper throughput.
I'm running the soap server on a JRUN 4 server, do you have any advice on j2ee settings. Do you have any advice on how to manipluate the pools and which pools! What settings do usually amend on your j2ee app server, or elsewhere
Thanks in advance
Jonathan
Scott Nichol <[EMAIL PROTECTED]> wrote:
I have run similar (threaded client) tests, but my results were not
similar to yours, in that the average response time for a request
remained fairly consistent.
The configuration of your Web server, servlet container and even
server OS can impact your results. All 3 likely have a pool of
threads and/or memory structures from which resources are allocated
to service requests. If the pools are small, your SOAP requests will
sit in the queue longer. Making sure the pools are large enough is
essential to obtain proper throughput.
Of course, this assumes the server processes have sufficient basic
resources like CPU and memory. If the server CPU is pinned or memory
paging starts, pool sizes for other resources are probably
inconsequential.
On 19 Jun 2003 at 0:05, Jonathan Roberts wrote:
> Hi All.
>
> I'm using soap and it's workign great for low load requests.
>
> However when the number of requests start increasing there seems to be a significant time lag associated with them.
>
> The requests are sent off using threading. The responses seem to come back in no specific order such that sometimes the first request is returned last or near last.
> For 70 requests, the system seems to take about 50 seconds to complete all tasks. When there is low load - the response is received almost instantaneously.
>
> Presubamly this is due to the noise on the channel - but is there any way of adding any (soap) settings such that this scenario is improved.
>
> Regards
>
> Jonathan
>
>
>
> ---------------------------------
> Want to chat instantly with your online friends? Get the FREE Yahoo!Messenger
Scott Nichol
Do not reply directly to this e-mail address,
as it is filtered to only receive e-mail from
specific mailing lists.
Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger
