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 "Øystein Grøvlen (JIRA)" <ji...@apache.org> on 2007/05/02 09:01:15 UTC
[jira] Closed: (DERBY-2586) BlobClob4BlobTest.tesPositionAgressive
takes very long time
[ https://issues.apache.org/jira/browse/DERBY-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Øystein Grøvlen closed DERBY-2586.
----------------------------------
Resolution: Fixed
With the fix applied, the run time is back to normal.
> BlobClob4BlobTest.tesPositionAgressive takes very long time
> -----------------------------------------------------------
>
> Key: DERBY-2586
> URL: https://issues.apache.org/jira/browse/DERBY-2586
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Reporter: Øystein Grøvlen
> Assigned To: Anurag Shekhar
> Fix For: 10.3.0.0
>
> Attachments: derby-2586.diff
>
>
> Dan reports that BlobClob4BlobTest.tesPositionAgressive takes very long to run:
> > In a test run (junit-all) of 5,816 fixtures that took 4124 seconds (~68mins) *three* fixtures took 53% of the total time.
> >
> > testPositionAgressive 1564.684 seconds
> > testNetworkServerSecurityMechanism 497.280 seconds
> > testTypesInActionStatement 128.928 seconds
> Knut Anders reports that this behavior is fairly new:
> > It seems like it started taking a lot more time at revision 530085. I had
> > run the tests at an earlier revision.
> This was a check-in for DERBY-2346. Since Anurag is currently on vacation, I will try to look into this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.