[
https://issues.apache.org/jira/browse/DERBY-4363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-4363:
-----------------------------------
Attachment: bmWithPatch.out
bmTrunk.out
benchmark.sh
Attached is 'benchmark.sh', which contains the simple script that I ran to
conduct a 15-item benchmark of the GROUP BY statement with and without
the DERBY-3002 patch applied.
Also attached is 'bmTrunk.out' and 'bmWithPatch.out', which are the benchmark
results of the script on a clean trunk build, and on a build with the
DERBY-3002 patch.
Unfortunately, the benchmark appears to show substantial performance
problems with the DERBY-3002 patch, so I'll have to look into the results more
deeply.
I suspect that this means that the DERBY-3002 patch cannot simply eliminate
the code patch which performs aggregation within the sort observer, because
the performance wins from doing such aggregation are substantial.
> Add simple benchmark for measuring GROUP BY performance
> -------------------------------------------------------
>
> Key: DERBY-4363
> URL: https://issues.apache.org/jira/browse/DERBY-4363
> Project: Derby
> Issue Type: Sub-task
> Components: Test, Tools
> Reporter: Bryan Pendleton
> Assignee: Bryan Pendleton
> Priority: Minor
> Attachments: benchmark.sh, bmTrunk.out, bmWithPatch.out,
> multiColumnBenchmark.diff, simpleBenchmark.diff
>
>
> As part of ROLLUP implementation (DERBY-3002), it will be helpful to be able
> to measure the performance of GROUP BY.
> Using the o.a.dT.perf.clients framework, this sub-task proposes to add a
> GroupByClient to the performance runner
> library; the GroupByClient will run GROUP BY statements against the Wisconsin
> benchmark database.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
