You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2006/11/19 00:47:38 UTC

[jira] Updated: (DERBY-2099) Make BasePage.getPageId() final

     [ http://issues.apache.org/jira/browse/DERBY-2099?page=all ]

Knut Anders Hatlen updated DERBY-2099:
--------------------------------------

    Attachment: getpageid.diff

> Make BasePage.getPageId() final
> -------------------------------
>
>                 Key: DERBY-2099
>                 URL: http://issues.apache.org/jira/browse/DERBY-2099
>             Project: Derby
>          Issue Type: Improvement
>          Components: Performance, Store
>    Affects Versions: 10.3.0.0
>            Reporter: Knut Anders Hatlen
>         Assigned To: Knut Anders Hatlen
>            Priority: Trivial
>         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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira