[ 
https://issues.apache.org/jira/browse/HADOOP-18426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18035182#comment-18035182
 ] 

ASF GitHub Bot commented on HADOOP-18426:
-----------------------------------------

github-actions[bot] commented on PR #4811:
URL: https://github.com/apache/hadoop/pull/4811#issuecomment-3483177090

   We're closing this stale PR because it has been open for 100 days with no 
activity. This isn't a judgement on the merit of the PR in any way. It's just a 
way of keeping the PR queue manageable.
   If you feel like this was a mistake, or you would like to continue working 
on it, please feel free to re-open it and ask for a committer to remove the 
stale tag and review again.
   Thanks all for your contribution.




> Improve the accuracy of MutableStat mean
> ----------------------------------------
>
>                 Key: HADOOP-18426
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18426
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: common
>    Affects Versions: 3.4.0
>            Reporter: Shuyan Zhang
>            Assignee: Shuyan Zhang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.4.0
>
>
> The current MutableStat mean calculation method is more prone to loss 
> accuracy because the sum of samples is too large. 
> Storing large integers in the double type results in a loss of accuracy. For 
> example, 9223372036854775707 and 9223372036854775708 are both stored as 
> doubles as 9223372036854776000. Therefore, we should try to avoid using the 
> cumulative total sum method to calculate the average, but update the average 
> every time we sample. All in all, we can process each sample on its own to 
> improve mean accuracy.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to