@mperham if you're curious, the benchmarks weren't particularly encouraging: https://github.com/tarcieri/fastcondition/commit/951d6b25ce34b3c4c59a51fcebf8cf9b80611b27 … /cc @halorgium @evanphx
-
-
Replying to @bascule
@bascule@mperham@halorgium Well, you need to expose the mutex to be locked seperately.1 reply 0 retweets 0 likes -
Replying to @evanphx
@evanphx@mperham@halorgium what do you mean by "locked separately"?1 reply 0 retweets 0 likes -
Replying to @bascule
@bascule@mperham@halorgium The point of a condvar is to give up control during a locked sequence. lock => work => wait => work => release1 reply 0 retweets 0 likes -
Replying to @evanphx
@evanphx@mperham@halorgium unless I'm mistaken, that's what it's doing every time cond.wait(mutex) is called1 reply 0 retweets 0 likes -
Replying to @bascule
@bascule@mperham@halorgium You're locking after a wait. The mutex is auto-locked after wait. How do you lock before the user does work?2 replies 0 retweets 0 likes -
Replying to @evanphx2 replies 0 retweets 0 likes
@halorgium @evanphx @mperham redone with explicit locks: https://github.com/tarcieri/fastcondition/blob/master/tasks/benchmark.rake …
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.