[
https://issues.apache.org/jira/browse/DERBY-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan resolved DERBY-3731.
------------------------------------
Resolution: Fixed
Derby Info: (was: [Patch Available])
Pulled out a commit on the 10.4 branch with revision 755636, since the rest of
the changes won't be backported.
Note that the first patches contributed by Kathey did go into both 10.4 and
10.3, but the later patches did not.
This means that the fix version is slightly inaccurate.
I don't expect to do any more changes for this issue. Feel free to close the
issue.
> 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.
