This is something that should be configurable & extendable in core.async really... but given how long it took to have this possibility with agents I am not holding my breath (not to mention it was never even considered for c.c/future).
On Tuesday, October 7, 2014 8:48:23 PM UTC+2, Brian Guthrie wrote: > > > On Sun, Oct 5, 2014 at 11:57 PM, Zach Tellman <ztel...@gmail.com > <javascript:>> wrote: > >> If I'm reading this correctly, you're using non-blocking thread pools for >> blocking operations on the sockets. Given more than N connections (last >> time I looked the thread pool's size was 42), you risk deadlock or at the >> very least poor average throughput. > > > I'd thought the thread pool's size was a function of your core count plus > some constant, which I believe is 42. But yes, that is a constraint, and > deadlock is a risk with too many concurrent connections. I haven't tried to > measure throughput yet but that seems like a reasonable next step. Thanks > for the code review! > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
