The full-scale document is approximately 300MB and has around 500K (or maybe 1M) elements.
The only way I can see to generate the document so I don’t have to change it when moving from temp to production is to set the database name to the production version and then have the code that uses it during construction add the temp name prefix dynamically. This will work and shouldn’t be too hard to retrofit to my existing code.
I don’t get any failure indication in the BaseX log, so if there’s a failure reported elsewhere, I don’t know where to find it.
The server has 4GB of RAM, which should be enough.
But, as I think more about this process, even if I was able to have the XSLT succeed, it’s wasteful and best avoided anyway.
Cheers,
E.
_____________________________________________ Eliot Kimber Sr. Staff Content Engineer O: 512 554 9368
servicenow
servicenow.comhttps://www.servicenow.com LinkedInhttps://www.linkedin.com/company/servicenow | Xhttps://twitter.com/servicenow | YouTubehttps://www.youtube.com/user/servicenowinc | Instagramhttps://www.instagram.com/servicenow
From: Liam R. E. Quin liam@fromoldbooks.org Date: Monday, April 21, 2025 at 7:22 PM To: Eliot Kimber eliot.kimber@servicenow.com, basex-talk@mailman.uni-konstanz.de basex-talk@mailman.uni-konstanz.de Subject: Re: [basex-talk] Way to record node IDs that does not depend on database name? [External Email]
________________________________ On Mon, 2025-04-21 at 17:19 +0000, Eliot Kimber via BaseX-Talk wrote:
This works fine at small scales, but when I attempt it with my 200K-link database, the XSLT transform either simply never completes or fails in the backgroujnd or would take so long to complete that it would be impractical.
Why does it fail? Why is it slow? Does it run out of memory? Is it reading a large input document?
Can you generate your database attributes in such a way that they don't need to be changed?
-- Liam Quin, https://www.delightfulcomputing.com/https://www.delightfulcomputing.com/ Available for XML/Document/Information Architecture/XSLT/ XSL/XQuery/Web/Text Processing/A11Y training, work & consulting. Barefoot Web-slave, antique illustrations: http://www.fromoldbooks.orghttp://www.fromoldbooks.org