Performance of Large WSDL files...
Don O Neill
I was just wondering if any of you have run into a performance problem with
large WSDL files. On our systems Windows 2000 or NT 4.0 if a WSDL file goes
over 15 or so methods the performance of the SOAP Server drops dramatically.
We've trace your application all the way through from start to finish and
the delay is inside the SOAP server as it loads the WSDL and WSML files. To
avoid this problem for now we have started breaking up our large WSDL files
into many smaller ones however this really is just a workaround the problem.
If anyone has seen this and found a better fix to the problem please let me
know. One last point we did installed SP 2 of the SOAP Server and no luck
in fact it got a little (not much) slower.
Example Web Service:
1 large WSDL file
70 Methods
71 K WSDL file
1000 Mhz Processor x2
512 MB RAM
Time Per call 800ms !!!
If Size reduced to 7K and about 10 methods
Time Per call 80ms
This seems to be a general WSDL file size issue, this problem can be
recreted using empty methods on any COM object so it's not related to the
functionality in the Web Service implementation.
I'm having trouble accepting that the file size alone can cause such an
increase and so I feel something is going wrong inside the SOAP Server
itself. Please remember the figures I'm quoting here do not include HTTP
Server communication they are the time from when the high level interface of
the SOAP Server is first called to when it returns.
Regards
Don.
Frank Mantek
WSDL/WSML files ?
If it is non-cached than this is "expected". Parsing the WSDL files is a
major job, doing this for every call could easily explain your observations.
Frank
"Don O Neill" <don...@eschergroup.com> wrote in message
news:et5Vv05DBHA.2020@tkmsftngp07...
Don O Neill
Is this an option on the high level interface of the SOAP Server ?
Our application that contains the MS SOAP Server does not implement any
caching itself, but we have considered this, it just seemed that the
performance decrease was not linear, and so seemed like a bug in the SOAP
Server itself.
Thanks for you feedback
Don.
"Frank Mantek" <nos...@microsoft.com> wrote in message
news:OcyurJ7DBHA.1400@tkmsftngp05...
Wolfgang Manousek
is this isapi or asp ?
your application contains a soap server? please describe the scenario in
more detail
"Don O Neill" <don...@eschergroup.com> wrote in message
news:#L4qjQ7DBHA.1900@tkmsftngp04...
Roger Wolter
bigger makes it take 10 time longer to parse? That doesn't sound to
mysterious to me. The way around this is to only parse the WSDL file once.
The ISAPI listener does this by default. If you are using the generated ASP
listener, it also does this by default. If you are calling mssoapinit for
every function call on the client or the server your performance isn't going
to be acceptable.
"Don O Neill" <don...@eschergroup.com> wrote in message
news:et5Vv05DBHA.2020@tkmsftngp07...
Don O Neill
via HTTP and its own implementation of the HTTP/1.1 protocol. There is no
ASP, no IIS etc involved. In the times I gave already we have isolated them
down to just the Invoke call so any HTTP overhead has been removed from our
test results. At present we are not caching the SOAP Server, we are working
on doing so however it's been a little problematic to say the least (on our
side). While caching may help reduce the problem I still can't believe that
a large XML document could take so long to load.
Regards
Don.
"Wolfgang Manousek" <wolfma@nospam_msft.com> wrote in message
news:u8M7Xo9DBHA.936@tkmsftngp05...
Wolfgang Manousek
document, we also prepare a lot of our internal infrastructure at that point
in time. we are looking into changes for the next release (especially with
the support of the import feature), but for now the solution is to hang on
to the soap server.
Wolfgang
"Don O Neill" <don...@eschergroup.com> wrote in message
news:OmC4kPGEBHA.1380@tkmsftngp05...