[
https://issues.apache.org/jira/browse/HDFS-13702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16524128#comment-16524128
]
Todd Lipcon commented on HDFS-13702:
------------------------------------
Removing all the HTrace stuff from the block reader path improved the
performance of TeraValidate by about 20%, reduced CPU consumption of the job in
LocalJobRunner mode by about 36%.
We could attempt to use the HTrace APIs in a fancier way to detect when tracing
is not enabled, but I think we may be better off just removing it entirely.
HTrace as a project is being retired. If we choose to re-introduce tracing (eg
using OpenTracing) we should make sure to benchmark it more thoroughly.
[~stack] what do you think?
> HTrace hooks taking 10-15% CPU in DFS client when disabled
> ----------------------------------------------------------
>
> Key: HDFS-13702
> URL: https://issues.apache.org/jira/browse/HDFS-13702
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: performance
> Affects Versions: 3.0.0
> Reporter: Todd Lipcon
> Priority: Major
>
> I am seeing DFSClient.newReaderTraceScope take ~15% CPU in a teravalidate
> workload even when HTrace is disabled. This is because it stringifies several
> integers. We should avoid all allocation and stringification when htrace is
> disabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
