You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@xml.apache.org by "Herreman, Christophe" <Ch...@barco.com> on 2002/01/18 10:01:03 UTC
Performance of SOAP RPC ?
Hello,
We are experiencing a problem using RPC; (Apache SOAP 2.2 + tomcat 4.01 +
10Mbit ethernet LAN).
When client and service are running on the same PC, a simple RPC call takes
about 25 msec for the roundtrip.
On the LAN the same RPC call takes about 250 msec !!!
Strangly, both CPUs are barely working at all (5%) and the network load is
low.
We are keeping the HTTP connection open and are re-using the Call object and
we are using application scope objects on the server.
Also we see that the SOAP messages are send in two packets: one for the
header and one for the enveloppe.
Appearently, the server is responding fast enough. We suspect that HTTP is
to blame.
Any ideas ?
What is the normal performance we may expect for RPC call using SOAP?
Thanks,
Chris.
Re: Performance of SOAP RPC ?
Posted by Radovan Janecek <ja...@systinet.com>.
Just yesterday I have tried Tomcat 3.2.3 as http transport plug-in for Wasp
and realized that it is very slow (more than 10 times slower than standalone
Wasp).
Radovan
Radovan Janecek
VP, Engineering, Systinet (formerly Idoox)
http://www.systinet.com
----- Original Message -----
From: "Herreman, Christophe" <Ch...@barco.com>
To: <so...@xml.apache.org>
Sent: Friday, January 18, 2002 10:01 AM
Subject: Performance of SOAP RPC ?
> Hello,
>
> We are experiencing a problem using RPC; (Apache SOAP 2.2 + tomcat 4.01 +
> 10Mbit ethernet LAN).
>
> When client and service are running on the same PC, a simple RPC call
takes
> about 25 msec for the roundtrip.
>
> On the LAN the same RPC call takes about 250 msec !!!
>
> Strangly, both CPUs are barely working at all (5%) and the network load is
> low.
>
> We are keeping the HTTP connection open and are re-using the Call object
and
> we are using application scope objects on the server.
>
> Also we see that the SOAP messages are send in two packets: one for the
> header and one for the enveloppe.
>
> Appearently, the server is responding fast enough. We suspect that HTTP is
> to blame.
>
> Any ideas ?
>
> What is the normal performance we may expect for RPC call using SOAP?
>
> Thanks,
> Chris.
>
Re: Performance of SOAP RPC ?
Posted by Radovan Janecek <ja...@systinet.com>.
Just yesterday I have tried Tomcat 3.2.3 as http transport plug-in for Wasp
and realized that it is very slow (more than 10 times slower than standalone
Wasp).
Radovan
Radovan Janecek
VP, Engineering, Systinet (formerly Idoox)
http://www.systinet.com
----- Original Message -----
From: "Herreman, Christophe" <Ch...@barco.com>
To: <so...@xml.apache.org>
Sent: Friday, January 18, 2002 10:01 AM
Subject: Performance of SOAP RPC ?
> Hello,
>
> We are experiencing a problem using RPC; (Apache SOAP 2.2 + tomcat 4.01 +
> 10Mbit ethernet LAN).
>
> When client and service are running on the same PC, a simple RPC call
takes
> about 25 msec for the roundtrip.
>
> On the LAN the same RPC call takes about 250 msec !!!
>
> Strangly, both CPUs are barely working at all (5%) and the network load is
> low.
>
> We are keeping the HTTP connection open and are re-using the Call object
and
> we are using application scope objects on the server.
>
> Also we see that the SOAP messages are send in two packets: one for the
> header and one for the enveloppe.
>
> Appearently, the server is responding fast enough. We suspect that HTTP is
> to blame.
>
> Any ideas ?
>
> What is the normal performance we may expect for RPC call using SOAP?
>
> Thanks,
> Chris.
>
RE: Performance of SOAP RPC ?
Posted by graham glass <gr...@mindspring.com>.
hi there,
the GLUE web services platform gets about 700 messages/second
on a standard PC. (http://www.themindelectric.com)
a lot depends on whether the web services platform makes
use of HTTP 1.1. persistent connections and how fast its XML
parser is.
HTTP is actually pretty efficient and not the culprit.
cheers,
graham
-----Original Message-----
From: Herreman, Christophe [mailto:Christophe.Herreman@barco.com]
Sent: Friday, January 18, 2002 3:01 AM
To: 'soap-dev@xml.apache.org'
Subject: Performance of SOAP RPC ?
Hello,
We are experiencing a problem using RPC; (Apache SOAP 2.2 + tomcat 4.01 +
10Mbit ethernet LAN).
When client and service are running on the same PC, a simple RPC call takes
about 25 msec for the roundtrip.
On the LAN the same RPC call takes about 250 msec !!!
Strangly, both CPUs are barely working at all (5%) and the network load is
low.
We are keeping the HTTP connection open and are re-using the Call object and
we are using application scope objects on the server.
Also we see that the SOAP messages are send in two packets: one for the
header and one for the enveloppe.
Appearently, the server is responding fast enough. We suspect that HTTP is
to blame.
Any ideas ?
What is the normal performance we may expect for RPC call using SOAP?
Thanks,
Chris.
RE: Performance of SOAP RPC ?
Posted by graham glass <gr...@mindspring.com>.
hi there,
the GLUE web services platform gets about 700 messages/second
on a standard PC. (http://www.themindelectric.com)
a lot depends on whether the web services platform makes
use of HTTP 1.1. persistent connections and how fast its XML
parser is.
HTTP is actually pretty efficient and not the culprit.
cheers,
graham
-----Original Message-----
From: Herreman, Christophe [mailto:Christophe.Herreman@barco.com]
Sent: Friday, January 18, 2002 3:01 AM
To: 'soap-dev@xml.apache.org'
Subject: Performance of SOAP RPC ?
Hello,
We are experiencing a problem using RPC; (Apache SOAP 2.2 + tomcat 4.01 +
10Mbit ethernet LAN).
When client and service are running on the same PC, a simple RPC call takes
about 25 msec for the roundtrip.
On the LAN the same RPC call takes about 250 msec !!!
Strangly, both CPUs are barely working at all (5%) and the network load is
low.
We are keeping the HTTP connection open and are re-using the Call object and
we are using application scope objects on the server.
Also we see that the SOAP messages are send in two packets: one for the
header and one for the enveloppe.
Appearently, the server is responding fast enough. We suspect that HTTP is
to blame.
Any ideas ?
What is the normal performance we may expect for RPC call using SOAP?
Thanks,
Chris.