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] Closed: (DERBY-2099) Make BasePage.getPageId() final
Date Sat, 18 Nov 2006 23:51:38 GMT
     [ http://issues.apache.org/jira/browse/DERBY-2099?page=all ]

Knut Anders Hatlen closed DERBY-2099.
-------------------------------------

    Fix Version/s: 10.3.0.0
       Resolution: Fixed

Committed revision 476662.

> 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
>             Fix For: 10.3.0.0
>
>         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

        

Mime
View raw message