[
https://issues.apache.org/jira/browse/DERBY-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-3818:
-----------------------------------
Derby Info: [Patch Available]
Fix Version/s: 10.5.0.0
Derby Categories: [High Value Fix, Performance] (was: [Performance, High
Value Fix])
> 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
> Fix For: 10.5.0.0
>
> 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.
