You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Steve Huston (JIRA)" <ji...@apache.org> on 2011/04/29 16:36:03 UTC
[jira] [Commented] (QPID-3236) Add high-resolution timestamps to
log files for debug situations
[ https://issues.apache.org/jira/browse/QPID-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026992#comment-13026992 ]
Steve Huston commented on QPID-3236:
------------------------------------
Good idea. I would like to see this enabled by a cmake setting, or the equivalent --enable-foo in autoconf.
> Add high-resolution timestamps to log files for debug situations
> ----------------------------------------------------------------
>
> Key: QPID-3236
> URL: https://issues.apache.org/jira/browse/QPID-3236
> Project: Qpid
> Issue Type: Task
> Reporter: Kim van der Riet
> Assignee: Kim van der Riet
>
> In some performance-related debug situations, it would be useful to see the time between logged events (in debug or trace mode). However, the standard log timestamp has a 1 second resolution, and it does not help matters when hundreds of events of interest all occur within the same second.
> I propose to add a #define in qpid/sys/posix/Time.cpp which would change the timestamp printed by the outputFormattedNow() method to an unformatted second/nanosecond output. This define would be uncommented and compiled in when needed, but remain commented out for normal use. A comment would explain its use.
> I am sure an equivalent change could also be made to the windows version in qpid/sys/windows/Time.cpp.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org