Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <810696505.1246285547433.JavaMail.jira@brutus>
Date: Mon, 29 Jun 2009 07:25:47 -0700 (PDT)
From: "Dag H. Wanvik (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-2099) Make BasePage.getPageId() final
In-Reply-To: <25530182.1163893538459.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Dag H. Wanvik updated DERBY-2099:
---------------------------------

    Derby Categories: [Performance]

> Make BasePage.getPageId() final
> -------------------------------
>
>                 Key: DERBY-2099
>                 URL: https://issues.apache.org/jira/browse/DERBY-2099
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>    Affects Versions: 10.3.1.4
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Trivial
>             Fix For: 10.3.1.4
>
>         Attachments: getpageid.diff
>
>
> When I did some profiling of Derby running with the test client in DERBY-1961, the profiling tool (Sun Studio's collect and analyzer) reported that BasePage.getPageId() used much CPU (although the method does almost nothing). Adding the 'final' keyword to the method definition seems to reduce the CPU usage and increase the throughput.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.