> SRW SOAP Average response time for the queries is 445ms. Not bad for
> a 50M database, but not what I was hoping for.
> I converted the client to use SRU. Average response time is 32ms.
> I then tried making the SRW message by hand, similar to building the
> SRU URL. Average response time is 46ms.
I think you just rediscovered the fact that SOAP tools are great to
generate stub code on the fly,
but this convenience is paid for in execution speed.
Using hand crafted SOAP messages is not that hard, it gives you the full
control over the stub code (which is yours), and executes faster.
The tricky part of every implementation is not the stub code anyway,
it's the server logic needed to perform the right requests in the data
base at hand, the parsing of queries, and the correct diagnostics/error
One could say that SOAP tools do the simple thing simpler, at a cost of
execution speed, but let you down on the important matter.
This seems the reason why we prefer to hand-code the SOAP messages in
many of our implementations - be it SRW, GOOGLE, AMAZONE ... search web
Marc Cromme, cand. polyt, Ph.D
Senior Developer, Project Manager
Index Data Aps
K°bmagergade 43, 2
1150 Copenhagen K.
tel: +45 3341 1000
fax: +45 3341 0101
INDEX DATA Means Business
for Open Source and Open Standards