Hi Dimitar,
Thanks for the info. I see that adding a document changes the database indexing status to off. A query to locate a document by node value in a database with 54k documents went from 3 seconds to 4 minutes.
I can image its difficult to balance performance in different aspects of the application and maintain database stability at the same time. For the past couple of weeks Ive tested query performance on a half dozen databases and BaseX queries were almost always quickest and never crashed even when running with lower memory.
Depending on how things go with my research I may be able to help test the index updating feature when you are ready for that.
Thanks,
Gary
Hi Gary,
I'm the one who's working on the index updating. As Michael said it's a
work
in progress, but I expect to finish my work soon. Most probably it will be
released at some point after 6.6 (which should be available on March 23).
Best regards,
Dimitar
Am Dienstag 15 März 2011, 10:01:20 schrieb Michael Seiferle:
Hi Gary,
yes this is true either way, still in 6.5.1. We are currently working on incremental index updates, but I unfortunately can't give you any hint on a release date.
For most use-cases recreating the indexes (OPTIMIZE [1]) works fine in day to day use, but we are aware that this might get a little annoying under some circumstances.
Thanks a lot for your feedback, feel free to discuss or ask for more information. --
Kind regards Michael
From: Gary Larsen [mailto:gary.larsen@envisn.com] Sent: Monday, March 14, 2011 8:08 PM To: 'basex-talk@mailman.uni-konstanz.de' Subject: Updates and indexing
Hi,
I was reading a thread in the mail list from Oct 2010 which states updates are not indexed:
https://mailman.uni-konstanz.de/pipermail/basex-talk/2010-October/000707.htm l
Is this still the case with version 6.5.1? When talking of updates does that mean whole document replacement (or deletion) as well as XQuery updates?
Thanks for any clarification,
gary