@brixen @dbussink any advice as to best practices for @rubinius here, specifically regarding performance? https://github.com/celluloid/celluloid/pull/280 …
-
New conversation
-
-
-
@bascule cheapest locking solution is probably using a Rubinius.synchronized(obj) block, where obj can be any object used as lock -
-
-
@dbussink@brixen seem plausible? https://github.com/celluloid/celluloid/commit/e9391dc363eadb252e369faf7e835f004a61a845 … seeing about 5% perf degradation, possibly just variance in the benchmark
End of conversation
New conversation -
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.