[ 
https://issues.apache.org/jira/browse/DERBY-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682895#action_12682895
 ] 

Myrna van Lunteren commented on DERBY-3731:
-------------------------------------------

The state of this issue is somewhat unclear for 10.4...But it seems clear for 
10.5. If there's no objection, I'd like to close it while I'm working on the 
10.5 release notes.

> Improve calculation of refSize in ClassSize.java 
> -------------------------------------------------
>
>                 Key: DERBY-3731
>                 URL: https://issues.apache.org/jira/browse/DERBY-3731
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.5.0.0
>            Reporter: Kathey Marsden
>            Assignee: Kristian Waagan
>            Priority: Minor
>             Fix For: 10.4.2.1, 10.5.0.0
>
>         Attachments: derby-3731-1a-refsize_from_properties.diff, 
> derby-3731-1b-refsize_from_properties.diff, 
> derby-3731-1b-refsize_from_properties.stat, 
> derby-3731-1c-refsize_from_properties.diff, 
> derby-3731-2a_update_of_policy_template.diff, derby-3731-3a-doc_changes.diff, 
> DERBY-3731_diff.txt
>
>
> java/engine/org/apache/derby/iapi/services/cache/ClassSize.java has a static 
> code block which calculates the size of a reference for the architecture.  
> This code could be improved by adding garbage collection before measuring 
> memory, to give a consistent  reading.     Also there have been suggestions 
> that we use os.arch or sun.arch.data.model to make the measurement more 
> reliable, especially on 64bit machines.

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

Reply via email to