|
Hi Troy,
There are two possible places you can modify to get
some performance improvements.
Modify the WSRMPolicy.xml in the config directory
(it should be in the classpath when you run) to change the
BaseRetransmissionInterval and AcknowledgementInterval.
In addition if you can modify the code, reduce the
values for the followings in the Constants.
long RMINVOKER_SLEEP_TIME =
2000L;
long SENDER_SLEEP_TIME = 2000L;
long
CLIENT_RESPONSE_CHECKING_INTERVAL = 500L;
We will soon put these in the property file so that
they can be easily modified.
According to the spec if we try to make a one
request/response type web service invocation reliable using WS-RM it requires 6
message transfers, but if we need to transfer several messages in a sequence
then we can reduce the percentage on overhead messages.
We decided all these values depending on the
interop tests that we had with various other implementations such as IBM and
Microsoft. But they may not reflect the optimal values for specific business
scenarios
Please update us with the results.
Thanks,
Jaliya
I am also
experiencing significant performance degradation when using
Sandesha for
RM. My web service needs to be able to handle relatively
high-rate invocations. I can tolerate some latency but I need
to keep
the throughput up.
How can I specify the parameters for the
timing constraints
(BaseRetransmissionInterval, AcknowledgementInterval,
etc)? Are there
any guidelines for setting these?
What
are some other things I can do to increase the
performance?
Thanks,
Troy
-----Original Message-----
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday,
November 15, 2005 9:18 PM
To: [EMAIL PROTECTED]; James D.; [email protected]
Subject:
Re: Response times from services using Sandesha
Hi James,
As per
the RM specification, for a single request/response web service
invocation,
there will be at least 6 messages need to be passed between
the two
parties to the communication. The protocol is design to handle
many
messages in a sequence, so the percentage of additional messages
become
less significant.
In addition, there are timing constraints such as
retransmission
interval
and acknowledgement interval etc. So RM is bit
time consuming quality
of
service.
Thanks,
Jaliya
----- Original Message
-----
From: Hughes, James D.
To: [email protected]
Sent:
Tuesday, November 15, 2005 3:22 PM
Subject: Response times from services
using Sandesha
To get familiar with Sandesha I've created a simple
service that returns
a
count of the number of times it has been called.
When I do call.invoke
it
takes several (five or so) seconds for the
result to come back using
Sandesha. If I use just Axis it comes back
immediately. Any ideas as to
the cause of such a long
delay?
Thanks,
James Hughes
The MITRE
Corporation
---------------------------------------------------------------------
To
unsubscribe, e-mail: [EMAIL PROTECTED]
For
additional commands, e-mail: [EMAIL PROTECTED]
|
