[jira] Assigned: (DERBY-2586) BlobClob4BlobTest.tesPositionAgressive takes very long time

["Øystein Grøvlen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DERBY-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Øystein Grøvlen reassigned DERBY-2586:
--------------------------------------

    Assignee: Anurag Shekhar  (was: Øystein Grøvlen)

Thanks Anurag for looking at this while on vacation.  Your patch looks good and I recommend it to be committed so that the runtime of the junit test suite gets back to normal.

As a side note, I do not understand why UTF8Reader buffers the converted characters. Would it not have been better to buffer the incoming bytes and rather convert characters on demand?

> BlobClob4BlobTest.tesPositionAgressive takes very long time
> -----------------------------------------------------------
>
>                 Key: DERBY-2586
>                 URL: https://issues.apache.org/jira/browse/DERBY-2586
>             Project: Derby
>          Issue Type: Bug
>            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.