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 "Kristian Waagan (JIRA)" <ji...@apache.org> on 2008/10/22 17:29:44 UTC

[jira] Assigned: (DERBY-3818) client Insert/retrieval of 18MB Clob is extremely slow in MultiByteClobTest

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

Kristian Waagan reassigned DERBY-3818:
--------------------------------------

    Assignee: Kristian Waagan

> 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: 10.5.0.0
>            Reporter: Kathey Marsden
>            Assignee: Kristian Waagan
>
> 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.