This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-16
Channels
- # beginners (11)
- # boot (21)
- # cider (12)
- # clara (6)
- # cljs-dev (7)
- # cljsjs (1)
- # cljsrn (62)
- # clojure (137)
- # clojure-austin (5)
- # clojure-italy (1)
- # clojure-nl (2)
- # clojure-russia (46)
- # clojure-spec (21)
- # clojure-uk (79)
- # clojurescript (56)
- # clr (1)
- # core-typed (1)
- # css (1)
- # cursive (3)
- # datomic (35)
- # docker (2)
- # emacs (20)
- # garden (3)
- # hoplon (8)
- # incanter (3)
- # jobs (12)
- # mount (5)
- # nginx (1)
- # off-topic (71)
- # om (8)
- # om-next (6)
- # onyx (4)
- # perun (3)
- # proton (2)
- # protorepl (5)
- # re-frame (35)
- # reagent (38)
- # ring (5)
- # ring-swagger (12)
- # rum (35)
- # spacemacs (2)
- # specter (5)
- # test-check (6)
- # yada (52)
oracle jdk SE download page provides 2 version: 8u111 and 8u112. which I should download? what oracle jdk even/odd numbered version means? is there any convention?
I usually just pick the latest, not sure if there's any even/odd criteria when selecting jdk for clojure
here's the exact jdk I installed and forget anything about it afterwards, no problems encountered so far: jre8-openjdk-headless
@mavbozo In general pick the latest version as it contains the most security patches. If it does not work with clojure it should be a bug in clojure as long as the major version is supported (JDK > 1.6 according to the clojure homepage)
QQ on saturating CPU when it comes to core.async and pipelines. I've got a task that I'm fairly sure is CPU limited (deserialising Protobuf/data transformations) and I can't seem to saturate CPU regardless of how many threads I throw at the pipeline. Anyone got any tips ideas on debugging this, I'm currently using about 60% CPU and would like to be at 90%+.
@poooogles pipelines are in-order. So if one item takes a long time to serialize it will hold up the rest of the pipeline. Also buffer sizes on channels can make a huge difference. I normally start at 2x the number of CPUs, that's on both the input and output of the pipeline.
I have other suggestions, but start with the channel buffer sizes.