Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
10.3.3.1, 10.4.2.1, 10.5.3.1, 10.6.2.2, 10.7.1.4, 10.8.3.3, 10.9.2.2, 10.10.1.1, 10.11.1.1
-
None
-
None
-
After the
DERBY-2130fix in trunk (10.11) I noticed that the repro attached to the issue (repro.sql) ran significantly slower on 10.11 vs 10.1 or 10.2 with the patch. I tried the patch with 10.3 and found that the query ran slower there.
10.1 - 13 seconds
10.2 with patch - 10 seconds
10.3 with patch - 69 seconds
10.11 with patch - 69 seconds
So there must have been some slowdown between 10.2 and 10.3 that was masked by theDERBY-2130bug.
To reproduce on 10.3
Merge theDERBY-2130fix from trunk
svn merge -x -b -c 1534465 https://svn.apache.org/repos/asf/db/derby/code/trunk
Run repro.sql attached toDERBY-2130
After the DERBY-2130 fix in trunk (10.11) I noticed that the repro attached to the issue (repro.sql) ran significantly slower on 10.11 vs 10.1 or 10.2 with the patch. I tried the patch with 10.3 and found that the query ran slower there. 10.1 - 13 seconds 10.2 with patch - 10 seconds 10.3 with patch - 69 seconds 10.11 with patch - 69 seconds So there must have been some slowdown between 10.2 and 10.3 that was masked by the DERBY-2130 bug. To reproduce on 10.3 Merge the DERBY-2130 fix from trunk svn merge -x -b -c 1534465 https://svn.apache.org/repos/asf/db/derby/code/trunk Run repro.sql attached to DERBY-2130
-
High Value Fix, Repro attached
Attachments
Issue Links
- is related to
-
DERBY-2130 Optimizer performance slowdown from 10.1 to 10.2
- Closed