[
https://issues.apache.org/jira/browse/HTRACE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15003662#comment-15003662
]
Colin Patrick McCabe commented on HTRACE-297:
---------------------------------------------
The change to heartbeat interval is to make it a more realistic test of
performance... a 1 ms heartbeat reduces performance. Similar with the change
from TRACE logging to INFO in the benchmark. Stripping the port is something I
should have done in HTRACE-294 but I forgot. It's not really important in this
unit test but it's more consistent to avoid putting a port on the remote.
Committed to 4.1, thanks!
> htraced: avoid serializing spans to json unless TRACE logging is enabled
> ------------------------------------------------------------------------
>
> Key: HTRACE-297
> URL: https://issues.apache.org/jira/browse/HTRACE-297
> Project: HTrace
> Issue Type: Bug
> Components: htraced
> Affects Versions: 4.0
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Attachments: HTRACE-297.001.patch
>
>
> We have been unconditionally serializing spans to JSON, but only logging them
> when TRACE logging is enabled. Profiling has revealed that this is a CPU
> bottleneck. Let's put "if" statement guards around the log messages to avoid
> doing this serialization unless it is really useful.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
