Thanks for taking the time for this very important issue. Looking forward to
patches/test-cases
from you. Please add them to bugzilla directly and one of us will look into it.
Thanks,
dims
--- Dennis Sosnoski <[EMAIL PROTECTED]> wrote:
> I've been doing some investigations into Axis performance
- Original Message -
From: "Kenneth Chiu" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, October 17, 2002 2:08 PM
Subject: Re: Axis performance
> On Tue, 15 Oct 2002, Steve Loughran wrote:
> > Interesting to see that FP to ascii conv
send the double as text, but
include a hint which can be used to speed up the FP
conversion. We haven't investigated this yet, though.
> - Original Message -
> From: "Scott Nichol" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday,
On Tue, 15 Oct 2002, Tom Jordahl wrote:
> But the nice thing is that the authors make the comment
> that their results might help to make Axis better. I
> would like to think that they might provide patches that
> would make things faster. This could be wishful thinking
> on my part
>
> --
>
> Regarding nagling, HTTP1.0 is so aggressively sub-optimal that it is
always
> tempting to turn it off, yet TCP_NODELAY on long haul links is both
> anti-social and often counter-productive. Maybe clients should decide
> dynamically whether to delay or not depending on whether or not the
endpoint
TED]>
Sent: Tuesday, October 15, 2002 9:03 AM
Subject: Re: Axis performance
> Something this paper does not touch upon that has been much discussed on
> the Apache SOAP lists is disabling the Nagle algorithm, i.e. calling
> setTcpNoDelay(true), on the client socket. Basically, wit
> Delayed ACK
> withholds the ACK for a packet for typically 200 ms when either the
> packet is not a full MAC frame or the preceeding packet is not a full
> frame, although the delay is cancelled if the server has data to send
to
> the client, in which case the ACK is sent with the data.
Correct
Something this paper does not touch upon that has been much discussed on
the Apache SOAP lists is disabling the Nagle algorithm, i.e. calling
setTcpNoDelay(true), on the client socket. Basically, with the Nagle
algorithm enabled (the default), the client TCP/IP stack sends each data
packet after
But the nice thing is that the authors make the comment that their results might help
to make Axis better. I would like to think that they might provide patches that would
make things faster. This could be wishful thinking on my part
--
Tom Jordahl
Macromedia Server Development
-O
Their tests were run back in May. We've had several multiples of performance
improvement since then. It would be interesting to run them again against the current
codebase.
--Glen
> -Original Message-
> From: Douglas Bitting [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 15, 20
10 matches
Mail list logo
