Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Thu, 24 Feb 2011 19:26:38 +0000 (UTC)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <1280117901.14169.1298575598513.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Created: (DERBY-5068) Investigate increased CPU usage on
 client after introduction of UTF-8 CcsidManager
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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: 10.7.1.1
            Reporter: Knut Anders Hatlen


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