Re: Asynchronous xmldb:store()?

"Lizzi, Vincent" <[email protected]>
Newsgroups gmane.text.xml.exist
Message-ID <MN2PR04MB5757BA127E1BBF0B87822A768E499@MN2PR04MB5757.namprd04.prod.outlook.com>
I have what seems like a very similar question: is there any way to make xmldb:store faster?

I've been observing, in a long-running process that stores thousands of documents at a time, is that as the database grows in size the time that it takes to store documents increases.

I thought about removing the collection index configuration temporarily to store documents first and then run reindex as a second step. However, the reindex process can take days on a large collection and there are no progress indicators to show whether the reindex is working or hung, so this doesn't seem like a good option.

Are there any suggestions on what could be done to make xmldb:store faster or asynchronous?

Thanks,
Vincent

_____________________________________________
Vincent M. Lizzi
Head of Information Standards | Taylor & Francis Group
[email protected]<mailto:[email protected]>




Information Classification: General
From: Len Schultz <[email protected]>
Sent: Wednesday, September 14, 2022 4:20 AM
To: Craig Berry via Exist-open <[email protected]>
Subject: [Exist-open] Asynchronous xmldb:store()?

Is there a way to have an XQuery script execute a xmldb:store(), then return data without waiting for the store to complete?  My queries can create rather large XML variables that I'd like to save for debugging, logging, and later inspection.  The stores can take quite a bit of time.  So I'd like to avoid the performance hit of storing the document on the query latency, and therefore the application latency.  Any suggestions for how to implement an asynchronous store?

--len

_______________________________________________
Exist-open mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/exist-open
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.