You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/07/23 14:07:04 UTC
[jira] [Commented] (PROTON-956) [proton-j] avoid some overhead when
sending frames if the trace logging isnt enabled and there is no frame
tracer
[ https://issues.apache.org/jira/browse/PROTON-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14638707#comment-14638707 ]
ASF subversion and git services commented on PROTON-956:
--------------------------------------------------------
Commit 13682652f635544e82c29aa16654fe5031a143db in qpid-proton's branch refs/heads/master from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=1368265 ]
PROTON-956: avoid overhead of creating frame and payload duplicate objects for logging or tracing if the logging is disabled and there is no tracer
> [proton-j] avoid some overhead when sending frames if the trace logging isnt enabled and there is no frame tracer
> -----------------------------------------------------------------------------------------------------------------
>
> Key: PROTON-956
> URL: https://issues.apache.org/jira/browse/PROTON-956
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-j
> Affects Versions: 0.9.1
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Priority: Minor
> Fix For: 0.10
>
>
> Currently there is some overhead when sending each frame to accomodate trace logging and frame tracing. This occurs even if the trace logging isnt enabled and there isn't a frame tracer set on the transport, it should be improved to only apply when it will be used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)