[
https://issues.apache.org/jira/browse/DERBY-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644941#action_12644941
]
Kristian Waagan commented on DERBY-3825:
----------------------------------------
Thanks for letting me know, Ole.
I'm not sure how this slipped though, guess I have to look at my
test-deployment scripts...
Committed fix to 10.4 with revision 711221.
I'm sorry for the noise.
> StoreStreamClob.getReader(charPos) performs poorly
> --------------------------------------------------
>
> Key: DERBY-3825
> URL: https://issues.apache.org/jira/browse/DERBY-3825
> Project: Derby
> Issue Type: Bug
> Components: JDBC, Store
> Affects Versions: 10.5.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Fix For: 10.4.2.1, 10.5.0.0
>
> Attachments: derby-3825-0a-preview.diff,
> derby-3825-1a-reset_readpositioninbuffer.diff,
> derby-3825-2a-internalReader_repositioning.diff,
> derby-3825-2a-internalReader_repositioning.stat,
> derby-3825-2b-internalReader_repositioning.diff,
> derby-3825-3a-simplification.diff
>
>
> StoreStreamClob.getReader(charPos) performs poorly because it resets the
> underlying stream and skips data until it reached the requested character
> position. Not only does the data has to be skipped, it also has to be decoded
> (UTF-8).
> The problem is exposed through EmbedClob.getSubString, which causes extremely
> bad performance for the client driver because the locator based Clob
> implementation uses this method.
> For the record, there is another read buffer size issue that exaggerates the
> problem (it will probably be handled under DERBY-3769, and also DERBY-3818).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
