[
https://issues.apache.org/jira/browse/DERBY-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681661#action_12681661
]
Kristian Waagan commented on DERBY-3731:
----------------------------------------
Committed patch 3a to trunk. This was only documentation updates.
Before resolving/closing this issue, we have to agree on whether to backport
the latest fixes to 10.4 and/or 10.3.
The original fix was ported to both 10.4 and 10.3, however there was a request
to not backport any other fixes to those branches. Is this request still
standing?
I have committed a change of the policy files to 10.4, but neither the fix nor
the documentation changes have been backported. If we don't backport, I think I
will revert that change on the 10.4 branch for consistency.
> 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.
