Bug #5077
closedC#.Net: This "Evaluate()" statement take more time and memory consumption in 9.9.1.8 version.
0%
Description
Below is statement: var evaluations = evaluator.Evaluate()
Files
Related issues
Updated by Michael Kay about 3 years ago
Firstly, you need to tell us what you are comparing it with.
Secondly, you need to tell us exactly what you are doing: provide us with sample code that we can execute, preferably including the code you use to measure performance. And tell us what the run-time environment is.
Thirdly, tell us what performance degradation you are seeing. If it's a 5% increase, that's not something we would consider worth investigating, because in any release, some things will go a bit faster and some a bit slower. If it's running 10 times slower, that's something we would want to look at.
Updated by Dipak Shinde about 3 years ago
Below are requested details:
-
- 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.
Updated by Dipak Shinde about 3 years ago
Dipak Shinde wrote:
Below are requested details:
- A per our business logic we have created rule(Xquery) and we are evaluating this with the help of evaluate method.
- 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.
Updated by Dipak Shinde about 3 years ago
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} ....................................
Updated by Dipak Shinde about 3 years ago
- File Saxon API Query.txt Saxon API Query.txt added
Dipak Shinde wrote:
Below are requested details:
- 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.
Updated by Dipak Shinde about 3 years ago
Please delete unnecessary comment, I am not able to delete comment.
Updated by Dipak Shinde about 3 years ago
Dipak Shinde wrote:
Please find new comment in attachments.
Updated by Michael Kay about 3 years ago
- Has duplicate Bug #5078: C#.Net: This "Evaluate()" statement take more time and memory consumption in 9.9.1.8 version. added
Updated by Michael Kay about 3 years ago
We're still waiting for answers to the same three questions:
(1) you say it takes longer in 9.9.1.8. Longer than what? What release are you comparing it with?
(2) we need to see the actual query and a sample source document that demonstrates the problem.
(3) we need to know what (space and time) measurement you have made, and how you made them.
Updated by Michael Kay almost 3 years ago
- Status changed from New to Closed
I am closing this as we do not have enough information to investigate it any further.
Please register to edit this issue