[
https://issues.apache.org/jira/browse/DERBY-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491506
]
Sunitha Kambhampati commented on DERBY-2586:
--------------------------------------------
fwiw, I also looked at the change and it looks good. I ran the
BlobClob4BlobTest on my linux box and before the change - it took 3197s, with
this change it took 211s.
Anurag>"I suspect the problem is with 4k buffer size in LOBStreamControl before
it moves the data to file."
do you plan to make some changes related to this in some other jira issue , if
so can you point me to that jira issue.
Thanks.
> 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.
