[Xapian-discuss] xapian performance
olly at survex.com
Fri Dec 1 03:33:33 GMT 2006
On Mon, Nov 27, 2006 at 09:19:39PM +0100, Arjen van der Meijden wrote:
> But I don't see any reports coming to my console when using omega??
Neither do I oddly. Omega's Xapian::Database is a global so I guess the
destructor doesn't get called so the database doesn't get closed - a
little suprising for a modern C++ compiler though. Normally this isn't
a problem as the destructor doesn't do anything exciting, but here we
want it to be called so it can report the stats.
The simplest workaround is to use "examples/quest" from xapian-core to
run the queries rather than omega. See --help for the parameters to pass.
> I was going to try and see if the debug logging would show me whether
> databases were actually closed, but that took so long, I didn't feel
> like waiting for more than half an hour for a query that - without
> logging - would only take 0.1 second... Nor was I able to figure out how
> to limit the logging to something much less verbose.
Just the messages (i.e. --enable-debug-verbose) shouldn't be too bad
especially if you log to a file, though it's certainly slower. You
can specify which messages types using a bitmap specified in env var
XAPIAN_DEBUG_FLAGS as the "HACKING" document describes. The categories
each cover quite a lot of messages though.
More information about the Xapian-discuss