[
https://issues.apache.org/jira/browse/LOGCXX-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941501#comment-13941501
]
Florian Seydoux commented on LOGCXX-361:
----------------------------------------
@Chand: as you said, really hard (I think) to have something which can be
consistent (OS version dependency, specific hardware, etc.)
>From very little test I've made on my host (windows 7 x64), log timestamp was
>synchronized (at millisecond precision) with
>boost::chrono::high_resolution_clock.
So for most hosts on OS > winXP, it's highly probable that the issue no longer
exist.
> 15-16 milliseconds granularity on Windows
> ------------------------------------------
>
> Key: LOGCXX-361
> URL: https://issues.apache.org/jira/browse/LOGCXX-361
> Project: Log4cxx
> Issue Type: Improvement
> Components: Layout
> Environment: Windows NT/2003
> Reporter: Sameer Gupta
> Assignee: Curt Arnold
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> I have noticed the message timestamps being logged are atleast 15-16
> milliseconds apart on windows NT/2003 systems even though the messages
> actually requested to be logged were just couple of milliseconds apart. This
> is due to the functions being used in the log4cxx code which are based on the
> SYSTEMTIME structure. The accuracy of these functions is 15-16 milliseconds
> at the most. I have tried to play around with the code and implemented
> performance counters to produce sub 15-16 milliseconds accuracy between two
> message timestamps. This will specially help the users who develop low
> latency applications.
>
> I am wondering if I can contribute my work to the project. Please let me know
> how I can join the project as a developer and what is the procedure to
> contribute. Opologies, if this has already been implemented.
>
> Regards,
> Sameer
--
This message was sent by Atlassian JIRA
(v6.2#6252)
