[jira] [Commented] (LOGCXX-361) 15-16 milliseconds granularity on Windows‏

["Chand Priyankara (JIRA)" <lo...@logging.apache.org>]

    [ https://issues.apache.org/jira/browse/LOGCXX-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867643#comment-13867643 ] 

Chand Priyankara commented on LOGCXX-361:
-----------------------------------------

Hi Sameer,

Log4CXX been silent for a while and is back again. We are pleased to get your help on fixing this issue. Please let us know your fix, so one of us can merge it to the trunk. Its great if you can attach a patch file.

Thanks.

> 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.1.5#6160)