ninn | An experimental implementation of nQUIC in Rust

arr is declared inside the function runArray so it won't be accessible from outside, you could perhaps update runArray function to return the array, like below:

Couple of things - I'm guessing your out of memory is due to not calling DBMS_XMLDOM.freeDocument(docXXX);

But as to the issue of performance - without specifics on time, it's difficult to say if there's an issue with the code or if that's essentially expected overhead associated with parsing out the related xmltype field values. My immediate impression is, precalculate and store the "distance" values (when the xml is inserted/updated/deleted). That way you can just query the data via straight sql without all the parsing overhead on the read side. You can store the calculated values in the xml or in a relational table if you want to keep your xml schema clean.