db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3791) Excessive memory usage when fetching small Clobs
Date Fri, 25 Jul 2008 11:45:31 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616856#action_12616856
] 

Knut Anders Hatlen commented on DERBY-3791:
-------------------------------------------

The patch looks fine to me.

Just to check that I've understood correctly, removing the BufferedInputStream won't affect
the performance negatively because the underlying stream gets its data from a byte array,
so buffering the data in another byte array on top of that won't improve the speed at which
data can be read. Is that about right?

> Excessive memory usage when fetching small Clobs
> ------------------------------------------------
>
>                 Key: DERBY-3791
>                 URL: https://issues.apache.org/jira/browse/DERBY-3791
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.2.2.0, 10.3.1.4, 10.4.1.3, 10.5.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>         Attachments: derby-3791-1a-buffer_fix.diff
>
>
> When investigating DERBY-3312 I found out that performance with the embedded driver has
decreased a lot as well.
> Analysis on trunk indicate excessive memory usage, causing high allocation and garbage
collection costs.
> I believe there was another major performance problem in 10.3, but it appears fixed in
trunk. I have not spent time identifying this problem.

-- 
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