> -----Original Message-----
> From: Z39.50 Next-Generation Initiative [mailto:[log in to unmask]] On Behalf
> Matthew J. Dovey
> Sent: Wednesday, January 05, 2005 7:48 PM
> > Man, that is one deeply doo-dooey toolkit.
> This is probably Axis.
I can see that there are another dozen messages on this topic, and
you've probably thrashed this out already, but let me toss in a couple
other thoughts here.
The servers are all running unoptimized Axis. When I'm seeing 32ms
response time, that means that I'm getting three responses from
individual Axis servers in that time. I'd run some earlier tests where
I had dummied out the search engine and was getting 10ms response time.
So, I don't think that Axis is a terribly bad toolkit.
Remember that my client is making and breaking 69 requests and responses
on 69 threads. For all I know, there may be some thread synchronization
code in Axis that is serializing somewhere.
I have a variant of my architecture where I send out 23 messages to
sub-federators who resend the messages to their three local databases.
That brings the response time down to 164ms for the plain SRW clients,
14ms for the plain SRU client and 30ms for the hand-built SRW client.