[
https://issues.apache.org/jira/browse/KUDU-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved KUDU-63.
-----------------------------
Resolution: Fixed
Fix Version/s: 0.9.0
> boost::condition_variable can't use monotonic time, has bad performance
> -----------------------------------------------------------------------
>
> Key: KUDU-63
> URL: https://issues.apache.org/jira/browse/KUDU-63
> Project: Kudu
> Issue Type: Bug
> Components: util
> Affects Versions: M3
> Reporter: Colin Patrick McCabe
> Assignee: Todd Lipcon
> Priority: Trivial
> Fix For: 0.9.0
>
> Attachments: condition.h
>
>
> {{boost::condition_variable}} can't use monotonic time. So when someone
> adjusts his wall-clock time forward a bunch of threads will stall out.
> The performance is also bad as evidenced by RPC benchmarks where we did a lot
> better just using a simple wrapper around {{pthread_cond_wait}}. The reason
> is because {{boost::condition_variable}} actually creates its own, separate
> mutex, which it uses instead of the one you pass in.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
