Project

Profile

Help

Actions
Send by e-mail Copy link

Bug #3288

closed

Performance of streaming with xsl:fork/xsl:for-each-group/@group-by

Added by Michael Kay almost 7 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Low
Assignee:
Michael Kay
Category:
Performance
Sprint/Milestone:
-
Start date:
2017-06-19
Due date:
% Done:

0%

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

Description

Although bug #3281 is now fixed, investigation of the bug showed a performance problem with streamed group-by. Specifically, there will be a Watch registered with the WatchManager every time a new group is encountered, and on each startElement() event, the WatchManager will go through this list of Watches sequentially to determine which of them match. Most of them won't match, but the cost of this search will increase with the number of groups, so applications involving a very large number of groups will become very inefficient.

Actions
Copy link
 #1

Updated by Michael Kay over 3 years ago

  • Description updated (diff)
  • Status changed from New to Closed

I have studied the behaviour of a streamed grouping test case in the debugger and the problem reported here appears not to exist.

Please register to edit this issue

Actions
Send by e-mail Copy link

Also available in: Atom PDF