You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kristian Waagan (JIRA)" <ji...@apache.org> on 2009/03/23 09:22:51 UTC
[jira] Closed: (DERBY-3805) Create a simple Blob performance
regression test
[ https://issues.apache.org/jira/browse/DERBY-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan closed DERBY-3805.
----------------------------------
Resolution: Fixed
Derby Categories: [Performance]
Closing the issue, as the first version of the test has been completed.
More work can be done, for instance investigate the performance with the client driver and add new/more tests.
> Create a simple Blob performance regression test
> ------------------------------------------------
>
> Key: DERBY-3805
> URL: https://issues.apache.org/jira/browse/DERBY-3805
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.5.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Attachments: derby-3805-1a-blobaccesstest.diff, derby-3805-1b-blobaccesstest.diff
>
>
> A simple Blob performance regression test should exist to make it easier to detect performance degradations.
> The test should be reasonably quick to complete.
> My plan is to focus on embedded first, then continue and enable all tests for client/server if possible.
> Depending on the relative performance of embedded and client/server, the parameters might have to be tweaked to achieve an acceptable test duration.
> Note that the test results will only be valid for runs performed on the same machine. The intended purpose is to run the test against a clean trunk first, followed by a run with the patch possibly affecting the Blob performance.
> Also note that the compared builds must have been built with the same sanity mode.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.