I have had these problems with SOAP2.2...I think that it is to do with the
way the message is parsed in memory...To get round the problem we moved to
using Axis which has all of the functionality that we are using in the Alpha
version.
-Original Message-
From: Juan Gargiulo [mailto:[EMAIL
Eh - no - most setups deal with some 10's of messages a second at the very
least; esp. when the RTT is short. With longer round trip times and real
long distatn conenctions you'd front it with apache anyway - so that
offloading of the stack would again give you 10-100's of connectioons even
on th
t;[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, November 12, 2001 9:09 PM
Subject: RE: Re: Performance problems
> Radovan,
>
> What was the size of your message? I've seen similar numbers with
> very small message sizes (~.03KB). Have you done any testing with
>
g.
Thanks,
Chuck
-Original Message-
From: janecek
Sent: Monday, November 12, 2001 12:22 PM
To: soap-user
Cc: janecek
Subject: Re: Performance problems
Since I got some follow-up questions, I just want to say it more
precisely:
This number does not mean a throughput. It means a
- Original Message -
From: "Serge Arsenault" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, November 12, 2001 8:50 PM
Subject: RE: Performance problems
> We cannot compare those 3 seconds with the 500 roundtrips per second. In
the first case, the 3
___
Serge Arsenault
-Original Message-
From: Radovan Janecek [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 12, 2001 1:22 PM
To: [EMAIL PROTECTED]
Subject: Re: Performance problems
Since I got some follow-up questions, I just want to say it more precisely:
This number does
dovan Janecek" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, November 12, 2001 2:10 PM
Subject: Re: Performance problems
> I meant 500 roundtrips. Client sends a request, server eats it and
produces
> response, client gets a response.
>
> R.
>
> -
vember 12, 2001 5:10 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Performance problems
>
>
> I meant 500 roundtrips. Client sends a request, server eats it
> and produces
> response, client gets a response.
>
> R.
>
> - Original Message -
> From: "
I meant 500 roundtrips. Client sends a request, server eats it and produces
response, client gets a response.
R.
- Original Message -
From: "William Brogden" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, November 12, 2001 2:55 PM
Subject: Re
)
> per second.
>
> Sincerely
>
> Radovan
>
> Radovan Janecek
> VP, Engineering, Systinet (formerly Idoox)
> http://www.systinet.com
>
> - Original Message -
> From: "Ian Snead" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
&g
"Ian Snead" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, November 12, 2001 1:21 PM
Subject: Re: Performance problems
>
> I'm a little confused. 3 seconds over HTTP is a
> performance problem? Sounds about average to me,
> especially with XML parsing
I'm a little confused. 3 seconds over HTTP is a
performance problem? Sounds about average to me,
especially with XML parsing involved at both
ends...please correct me if this doesn't make
sense.
Anybody got a good reference URL to a digest of
the SOAP performance debate?
Cheers!
Ian
[EMAIL PRO
12 matches
Mail list logo
