Project

Profile

Help

Bug #5583

closed

Slower execution time of Saxon-EE 11.3 compared to 10.8 for some transformations

Added by Johan Gheys about 1 month ago. Updated about 1 month ago.

Status:
Duplicate
Priority:
Normal
Assignee:
Category:
Performance
Sprint/Milestone:
-
Start date:
2022-06-28
Due date:
% Done:

0%

Estimated time:
Legacy ID:
Applies to branch:
11, trunk
Fix Committed on Branch:
Fixed in Maintenance Release:
Platforms:

Description

When upgrading from Saxon-EE 10.8 to 11.3, we notice that most transformations require a bit more time, which of course is always possible when there is a new engine under the bonnet. However, for one of our transformations (see attachment) the increase was significant: from 108 s to 164 s (+52%). Hopefully, this test case gives you enough information for further optimisation.


Files

performance.zip (79.3 MB) performance.zip Johan Gheys, 2022-06-28 17:48
performance-2.zip (12.6 MB) performance-2.zip Johan Gheys, 2022-06-29 10:38
Actions #1

Updated by Michael Kay about 1 month ago

Thanks for reporting it. I'll take a look at it on my return from vacation next week.

Actions #2

Updated by Johan Gheys about 1 month ago

OK, thank you, I look forward to your return. In any case, enjoy your holiday to the full.

Actions #3

Updated by Johan Gheys about 1 month ago

I have uploaded a smaller test set that still has the same phenomenon (29 s with Saxon-EE 10.8 and 44 s with 11.3 (+52%)) so that testing and debugging can be done more efficiently.

Actions #4

Updated by Michael Kay about 1 month ago

My colleagues are investigating the problem and the suspicion currently falls on recently resolved bug 5539.

Actions #5

Updated by Michael Kay about 1 month ago

  • Tracker changed from Support to Bug
  • Category set to Performance
  • Status changed from New to Duplicate
  • Assignee set to Michael Kay
  • Applies to branch trunk added

We have confirmed that this is the problem described in bug #5539, which will be fixed in the next maintenance release.

Actions #6

Updated by Johan Gheys about 1 month ago

Thanks for the investigation and feedback. With this fix, the performance of version 11.4 will be back to what we are used to: exceptional.

Please register to edit this issue

Also available in: Atom PDF