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] [Updated] (DERBY-5068) Investigate increased CPU usage on client after introduction of UTF-8 CcsidManager
Date Mon, 16 May 2011 11:28:47 GMT

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

Knut Anders Hatlen updated DERBY-5068:

    Attachment: d5068-2b.diff

Attaching a new patch (2b) with the following changes from the 2a patch:

- Added test case to Utf8CcsidManagerClientTest to verify that we don't silently ignore unmappable

- Changed Utf8CcsidManager.encode() to raise exception when unmappable character or malformed
input is detected.

- Made Utf8CcsidManager.convertFromJavaString() use CharsetEncoder.encode(String) instead
of String.getBytes(String) so that umappable character/malformed input isn't silently ignored.

All the regression tests ran cleanly with the patch.

> Investigate increased CPU usage on client after introduction of UTF-8 CcsidManager
> ----------------------------------------------------------------------------------
>                 Key: DERBY-5068
>                 URL: https://issues.apache.org/jira/browse/DERBY-5068
>             Project: Derby
>          Issue Type: Task
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>         Attachments: d5068-1a.diff, d5068-2a.diff, d5068-2a.stat, d5068-2b.diff
> While looking at the performance graphs for the single-record select test during the
last year - http://home.online.no/~olmsan/derby/perf/select_1y.html - I noticed that there
was a significant increase (10-20%) in CPU usage per transaction on the client early in October
2010. To be precise, the increase seems to have happened between revision 1004381 and revision
1004794. In that period, there were three commits: two related to DERBY-4757, and one related
to DERBY-4825 (tests only).
> We should try to find out what's causing the increased CPU usage and see if there's some
way to reduce it.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message