Bug #5078
closedC#.Net: This "Evaluate()" statement take more time and memory consumption in 9.9.1.8 version.
0%
Description
-
- A per our business logic we have created rule(Xquery) and we are evaluating this with the help of evaluate method. 2 XQuery:
let $gReturnDataState := element{'ReturnDataState'} {''} let $gSchA...................
for $ReturnDataState at $currentReturnDataStatePos in if(....................
let $genSchA := false() let $genAllRealTangibleProperty...........
x:AllPropEndYrTotal x:ReturnState/x:ReturnDataState/x:SchA/x:AllRealTangibleProperty/x:AllPropEndYrTotal {$AllPropEndYrTotalData} ....................................
Code: XdmValue evaluations = evaluator.Evaluate();
- For few rules XQuery execution takes greater than 30GB memory.
Files
Related issues
Updated by Dipak Shinde about 3 years ago
- File Saxon API Query.txt Saxon API Query.txt added
Please find the attachment for XQuery.
Updated by Michael Kay about 3 years ago
We can't investigate a problem unless we can reproduce it. A query with lots of ellipses (....) is no use for diagnostics. With performance problems, the devil is always in the detail, so we need all the detail.
Your question says "9.9.1.8 takes more time and memory" but you haven't said what you are comparing with or how you are measuring it.
The biggest factor affecting memory use is usually the size of the source document being queried. How big is the source document?
Updated by Dipak Shinde about 3 years ago
Sorry, The source document is only 4.28MB.
Updated by Michael Kay about 3 years ago
Please try to package up your query and source document in a form that we can run it.
Updated by Michael Kay about 3 years ago
- Is duplicate of Bug #5077: C#.Net: This "Evaluate()" statement take more time and memory consumption in 9.9.1.8 version. added
Please register to edit this issue