On Thursday, July 21, 2016 at 6:15:46 AM UTC+2, James Reeves wrote: > > On 21 July 2016 at 05:05, Ashish Negi <thisismy...@gmail.com <javascript:> > > wrote: > >> with core async `go` you can not do blocking IO or any time consuming >> work. >> `go` uses fixed threadpool (no of cpus + 2 or something). >> and in your async-handler you are using `<!! c` which is blocking . >> https://clojure.github.io/core.async/ >> >> Try with `future`. https://clojuredocs.org/clojure.core/future >> > > While futures will work, it's worth pointing out you'd get the same result > just by increasing the thread count on the adapter. Either way you're using > up a thread per request. > > Since the database functions are not asynchronous, core.async isn't really > useful in this context. My suggestion would be to drop it altogether. > > - James >
http-kit threadpool was definitely bottleneck, and probably hakiri-cp connection pool. I reverted to initial version without core.async and bumped both pools to 128 and now CPU is fully saturated, and performance is much better. Comparable to Go version I wrote, maybe even better. Thanks you both for your time :) -- 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.
