[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: XML versus SOAP/WSDL Performance
HI,
First, thanks for the reference.
Now, we all recognize that there is a wide range of systems that are to
be managed. For high-end systems with a separate processor for management,
the processing and memory are not two much an issue, but for other systems,
and especially systems where the same CPU is used for the management
as is used for the functionality of the box, CPU usage is probably
more important than memory usage.
In the reference, there were several things that were implied that
were pretty scary. First, it looks like there are no rules like in
the SMI to keep the schema from being changed. It appeared that the
data type of an element could be changed.
Secondly, the overhead of the basic parsing of XML (the reading the
"document" as text and dealing with the "quoted" chars such as >
and varying strings does use CPU cycles. It seems that all that
use XML just ignore this overhead. Do you know of any performance
studies on this?
At 12:51 PM 9/20/2002 +0200, Aiko Pras wrote:
>Hi all
>
>Recently I've had a number of discussions on the performance differences between network management approaches that use XML technology, and approaches that use web services (SOAP/WSDL). Is there anyone who has real experience in this area, or know pointers to studies on this?
>
>I want to create a list of potential performance problems. I'm aware of the following issues thusfar:
>- SOAP/WSDL is more verbose than plain XML. Therefore more
> bandwidth (and memory) will be needed.
>- downloading WSDL descriptions may be time consuming. In case
> of standardized descriptions, it seems possible however to
> caching or even hard-code them.
>- WSDL descriptions allow the inclusion of newly defined data types,
> which must be downloaded from somewhere via the web. This may take
> a lot of time.
>
>Useful reference i found:
>http://www-106.ibm.com/developerworks/webservices/library/ws-testsoap/#h3
>
>Aiko
Regards,
/david t. perkins
--
to unsubscribe send a message to xmlconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/xmlconf/>