Hi Christian,
This is still sth. I don't quite get: does the second query take 0.5 or 13 seconds?
Actually we are doing two things. 1) We are firing the query through Java API QueryProcessor. 2) we are iterating the results to get serialize items.
while firing the query ("transaction/*[local-name() ne 'traInfo']"). it took 13 seconds while iterating over the resultset it will takes 0.5 secs.
Query will return around 94 lacks items.
So there are 94 child element that are not named "traInfo", but "lacks"? Two more questions.. What's the total number of child nodes
(try count(/transaction/*)?
There are 94 lacks child element that are not names "traInfo" as result
of *"transaction/*[local-name() ne 'traInfo']"* query.
Total child elements are around 1.01 crores. result of
(try count(/transaction/*).
So, I was wondering apart from query change, is there any baseX tuning or configuration changes should I do to further improve time from 13 secs.
The query profiling results suggest that some additional time is spent for checking namespaces. Maybe the following query is slightly faster:
transaction/*[local-name() ne 'traInfo']
I tried the above suggested query, It takes the same time to execute as well as loop iteration.
Regards,