db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anurag Shekhar (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2586) BlobClob4BlobTest.tesPositionAgressive takes very long time
Date Tue, 24 Apr 2007 18:11:15 GMT

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

Anurag Shekhar commented on DERBY-2586:
---------------------------------------

Easiest way of providing buffering over normal stream is to wrap it under BufferedInputStream
I am trying out that change to see if it improves significant performance improvement.

I suspect the problem is with 4k buffer size in LOBStreamControl before it moves the data
to file. I think i need to make this larger. While debugging I noticed even very large clob
are kept in memory so all the test case of BlobClob4BlobTest.testPositionAgressive used to
operate on in memory string. Now moving it onto stream has made is slow (this also explains
why DERBY-2450 remained unexposed). 

> 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: Øystein Grøvlen
>             Fix For: 10.3.0.0
>
>
> 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.


Mime
View raw message