Thank you Christian.
It seems that the resource index is not persistent, But rebuilt in memory at the first index access after the collection is opened. For my 3 M documents collection, it takes about 250 secs to respond to the first db:open('mycoll','mydoc') query. Following queries responds in millisecs before the collection gets opened again.
From your experience,
What could be the good way to handle a collection of several millions documents, With about ten thousands inserted/updated documents once a week ?
Best regards, Fabrice
-----Message d'origine----- De : Christian Grün [mailto:christian.gruen@gmail.com] Envoyé : lundi 18 mars 2013 15:32 À : Fabrice Etanchaud Cc : basex-talk@mailman.uni-konstanz.de Objet : Re: [basex-talk] seeking for a document in a collection with a million documents is very slow
Hi Fabrice,
yes, the document index is updated with each updating command. If you perform numerous updates, you may get better performance by switching AUTOFLUSH off [1]. Another alternative to speed up multiple update operations is to use XQuery for updates. Due to the pending update list semantics, however, It will require more main memory.
Christian
[1] http://docs.basex.org/wiki/Options#AUTOFLUSH ___________________________
Dear all,
From what I read in the documentation, My problem seems to be related to the update of the resource index.
Is this index updated after each add/replace/delete command, Or at the end of the commands' list ?
Last, could you please tell me if replace is equivalent to delete+add ?
Best, Fabrice