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)" <qp...@incubator.apache.org> on 2009/10/16 17:35:31 UTC

[jira] Created: (QPID-2150) Excessive warnings about Timer woken up late on Windows

Excessive warnings about Timer woken up late on Windows
-------------------------------------------------------

                 Key: QPID-2150
                 URL: https://issues.apache.org/jira/browse/QPID-2150
             Project: Qpid
          Issue Type: Improvement
          Components: C++ Broker
    Affects Versions: 0.6
         Environment: Windows
            Reporter: Steve Huston
             Fix For: 0.6


The C++ broker when running on Windows, shows a lot of warning messages like:

2009-10-15 21:48:37 warning Timer woken up 15ms late

The lateness is usually between 10 and 15 msec, owing to the relative imprecision in waking up a thread on Windows. I have two suggestions for resolving this:

1. Change the message from warning to debug. I'm a bit concerned that, regardless of platform, if users of a product where speed is an issue start seeing messages about timers waking up late, they may be concerned, without any cause probably. I'm thinking that the only people interested in this message are those diagnosing things who may want to enable debug messages.

2. Allow a platform-specific value for the threshold at which lateness prompts a message. For example, the current 10 msec limit is tighter than is useful for Windows - 30msec would be better.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


[jira] Resolved: (QPID-2150) Excessive warnings about Timer woken up late on Windows

Posted by "Steve Huston (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Huston resolved QPID-2150.
--------------------------------

    Resolution: Fixed
      Assignee: Steve Huston

Thanks very much for the quick feedback, Andrew. Changed the threshold to 50 msec, left log level alone. Fixed in trunk r826093.


> Excessive warnings about Timer woken up late on Windows
> -------------------------------------------------------
>
>                 Key: QPID-2150
>                 URL: https://issues.apache.org/jira/browse/QPID-2150
>             Project: Qpid
>          Issue Type: Improvement
>          Components: C++ Broker
>    Affects Versions: 0.6
>         Environment: Windows
>            Reporter: Steve Huston
>            Assignee: Steve Huston
>             Fix For: 0.6
>
>
> The C++ broker when running on Windows, shows a lot of warning messages like:
> 2009-10-15 21:48:37 warning Timer woken up 15ms late
> The lateness is usually between 10 and 15 msec, owing to the relative imprecision in waking up a thread on Windows. I have two suggestions for resolving this:
> 1. Change the message from warning to debug. I'm a bit concerned that, regardless of platform, if users of a product where speed is an issue start seeing messages about timers waking up late, they may be concerned, without any cause probably. I'm thinking that the only people interested in this message are those diagnosing things who may want to enable debug messages.
> 2. Allow a platform-specific value for the threshold at which lateness prompts a message. For example, the current 10 msec limit is tighter than is useful for Windows - 30msec would be better.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


[jira] Commented: (QPID-2150) Excessive warnings about Timer woken up late on Windows

Posted by "Andrew Stitcher (JIRA)" <qp...@incubator.apache.org>.
    [ https://issues.apache.org/jira/browse/QPID-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766590#action_12766590 ] 

Andrew Stitcher commented on QPID-2150:
---------------------------------------

I have a couple of things to add:

1. It would make sense not to warn for times less than the timer resolution. I didn't do this mostly due to laziness!

2. Really the timer code doesn't have any idea what the real criteria for warning is as it doesn't know what constraints the Timer clients are running under. So the warning is set fairly tight.

Given that the timer isn't being used for anything very sensitive to small delays putting the warning up to 30ms or even 50ms wouldn't be a problem for all platforms.

> Excessive warnings about Timer woken up late on Windows
> -------------------------------------------------------
>
>                 Key: QPID-2150
>                 URL: https://issues.apache.org/jira/browse/QPID-2150
>             Project: Qpid
>          Issue Type: Improvement
>          Components: C++ Broker
>    Affects Versions: 0.6
>         Environment: Windows
>            Reporter: Steve Huston
>             Fix For: 0.6
>
>
> The C++ broker when running on Windows, shows a lot of warning messages like:
> 2009-10-15 21:48:37 warning Timer woken up 15ms late
> The lateness is usually between 10 and 15 msec, owing to the relative imprecision in waking up a thread on Windows. I have two suggestions for resolving this:
> 1. Change the message from warning to debug. I'm a bit concerned that, regardless of platform, if users of a product where speed is an issue start seeing messages about timers waking up late, they may be concerned, without any cause probably. I'm thinking that the only people interested in this message are those diagnosing things who may want to enable debug messages.
> 2. Allow a platform-specific value for the threshold at which lateness prompts a message. For example, the current 10 msec limit is tighter than is useful for Windows - 30msec would be better.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org