Happy to hear that. Thanks for following up, and good luck!
Sam Neth
Lead Engineer
MarkLogic Corporation
On Apr 15, 2011, at 8:05 AM, Mike Sokolov wrote:
Sam - thanks for the input; I think you can ignore this. There was something
funky in our Java layer which has now apparently vanished (I
Sam - thanks for the input; I think you can ignore this. There was
something funky in our Java layer which has now apparently vanished (I
updated the component to a newer version) - it must have been including
some overhead in our system beyond just the XCC traffic and deserialization.
Now I
On 4/14/2011 4:41 PM, Sam Neth wrote:
By "cold" do you mean immediately following a server restart? Is each
"cold" run a new Java process? If so, you probably have some
class-loader activity in your measurement. A fair bit of the
difference is probably an authentication round-trip. Might al
By "cold" do you mean immediately following a server restart? Is each "cold"
run a new Java process? If so, you probably have some class-loader activity in
your measurement. A fair bit of the difference is probably an authentication
round-trip. Might also be some penalty for DNS resolution.
I'm working on optimizing some queries on one of our MarkLogic sites
using cq's profiling feature and also looking at query times in our
logs, and they seem oddly out of sync.
The times in our logs are based on wrapping calls to XCC
Session.submitRequest() between calls to Java
System.currentT
