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

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

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

   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.




> BlockDecompressorStream#rawReadInt wastes about 1% of overall CPU cycles 
> creating new EOFException
> --------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-19292
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19292
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: compress, io
>    Affects Versions: 3.3.6
>            Reporter: Benoit Sigoure
>            Assignee: Benoit Sigoure
>            Priority: Major
>         Attachments: 
> HADOOP-19292-Don-t-create-new-EOFException-in-BlockD.patch
>
>
> On our HBase clusters, while looking at CPU profiles, I noticed that about 1% 
> of overall CPU cycles are spent under BlockDecompressorStream#rawReadInt just 
> throwing EOFException. This could be easily avoided.



--
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