This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-09-13
Channels
- # aws-lambda (21)
- # beginners (8)
- # boot (67)
- # braveandtrue (2)
- # cider (12)
- # cljs-dev (38)
- # cljsjs (87)
- # cljsrn (11)
- # clojure (307)
- # clojure-austin (29)
- # clojure-finland (1)
- # clojure-italy (9)
- # clojure-russia (19)
- # clojure-spec (71)
- # clojure-uk (33)
- # clojurescript (109)
- # clojutre (1)
- # core-async (2)
- # cursive (24)
- # datomic (11)
- # devops (5)
- # ethereum (5)
- # figwheel (2)
- # hoplon (25)
- # ipfs (1)
- # jobs (1)
- # luminus (17)
- # off-topic (2)
- # om (38)
- # om-next (3)
- # onyx (166)
- # other-lisps (1)
- # proton (5)
- # re-frame (15)
- # reagent (45)
- # ring (2)
- # spacemacs (6)
- # specter (12)
- # untangled (58)
- # yada (23)
I don't know. Try it!
ok, I'll rephrase the question: anyone any experience using beta versions of aleph and manifold on latest yada? 🙂
You could run the yada tests. If they pass you'd be unlikely to run into major issues
I'm interested what's in the latest betas
we're running into 'too many open files' issues in production, when the system is under load
I don't think it has anything to do with yada or the aleph server, but is on the aleph client connection pool (this server acts as a proxy for other services)
Ah. Ok.
You could use http-kit instead?
and I haven't checked lately, but it was just impossible to control the connection pool
Have you tried the new betas? The surface between yada and aleph is quite small
It could work fine
@stijn i've used beta versions of aleph and manifold in the past with yada without difficulty
ok thanks @mccraigmccraig