[
https://issues.apache.org/jira/browse/LOGCXX-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thorsten Schöning resolved LOGCXX-361.
--------------------------------------
Resolution: Not A Problem
log4cxx uses apr_time_now which provides microseconds on supported platforms.
As mentioned in the comments, if a higher resolution of apr_time_now is needed,
this should be suggested to the APR project. Additionally, if Windows NT and
2003 where chosen by purpose, those platforms are not supported anymore by
Microsoft itself, so we shouldn't care much as well. All somewhat current
versions of Windows seem to provide a high resolution with apr_time_now.
I'm closing this for now.
> 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.4.14#64029)
