db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3818) client Insert/retrieval of 18MB Clob is extremely slow in MultiByteClobTest
Date Wed, 29 Oct 2008 14:55:44 GMT

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

Kristian Waagan updated DERBY-3818:

    Attachment: derby-3818-1a-enable_client_test.diff

Patch 1a enables the client test.

The poor performance has been resolved by other patches, most probably DERBY-3825 and DERBY-3769.
For me, MultiByteClobTest takes a little less than 1 minute with embedded only and around
2 minutes with both embedded and client tests.
I plan to commit the patch tomorrow.

> client Insert/retrieval of 18MB  Clob is extremely slow  in MultiByteClobTest
> -----------------------------------------------------------------------------
>                 Key: DERBY-3818
>                 URL: https://issues.apache.org/jira/browse/DERBY-3818
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Network Client
>    Affects Versions:
>            Reporter: Kathey Marsden
>            Assignee: Kristian Waagan
>             Fix For:
>         Attachments: derby-3818-1a-enable_client_test.diff
> In the test memory.MultiByteClobTest that was added for DERBY-3741, the client version
of the test took 525000ms vs 9578ms for embedded, so I disabled the client test for now. 
The client test should be analyzed to determine why Clob handling is so slow.   I am not sure
if the problem is on the insert, the retrieval or both.  Once this issue is resolved it would
be good to enable the test for client.  

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message