You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Justin Ross (JIRA)" <ji...@apache.org> on 2013/07/29 20:37:48 UTC
[jira] [Updated] (QPID-2938) Logging excessive warnings in Timer
code affects performance.
[ https://issues.apache.org/jira/browse/QPID-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Ross updated QPID-2938:
------------------------------
Fix Version/s: 0.10
> Logging excessive warnings in Timer code affects performance.
> -------------------------------------------------------------
>
> Key: QPID-2938
> URL: https://issues.apache.org/jira/browse/QPID-2938
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.6
> Reporter: Alan Conway
> Assignee: Alan Conway
> Fix For: 0.10
>
>
> The Timer code logs a warning if a timer callback is started late or overruns the start time for the next callback.
> In cases where there are a lot of these warnings, the time taken to do the logging itself severly worsens the situation. You can provoke such a warnings storm by starting a broker in a cluster and running:
> qpid-cpp-benchmark -q4 --send-arg --ttl=10000
> The log shows timer events that are increaesingly late and overrun by up to 30 seconds, and the test is very slow to complete, I gave up after 2 minutes when the lateness was up to 90 seconds.
> This warning storm has also been seen with out clustering but with a store, see https://bugzilla.redhat.com/show_bug.cgi?id=629756
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org