This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-01-18
Channels
- # admin-announcements (90)
- # alda (1)
- # aws (23)
- # beginners (60)
- # boot (217)
- # cljs-dev (20)
- # cljsjs (23)
- # cljsrn (85)
- # clojars (28)
- # clojure (101)
- # clojure-art (1)
- # clojure-berlin (10)
- # clojure-dev (16)
- # clojure-my (2)
- # clojure-russia (194)
- # clojure-sg (7)
- # clojure-ukraine (1)
- # clojured (1)
- # clojurescript (99)
- # clojurex (1)
- # community-development (6)
- # core-matrix (11)
- # cursive (26)
- # datomic (51)
- # euroclojure (30)
- # hoplon (560)
- # jobs (44)
- # ldnclj (34)
- # mount (23)
- # music (3)
- # off-topic (10)
- # om (145)
- # onyx (3)
- # perun (38)
- # portland-or (2)
- # proton (55)
- # re-frame (64)
- # reagent (26)
- # ring-swagger (3)
- # spacemacs (21)
- # sydney (3)
- # yada (1)
Ok cool
@cfleming: My own results http://numergent.com/2016-01/AWS-Lambda-Clojure-and-ClojureScript.html
those were pretty interesting. what version of Clojure were you using?
I'd be curious to see the timings with 1.8.0-RC5 (or soon 1.8.0) with a lambda compiled with direct linking
@alexmiller: 1.7, didn’t try with 1.8
RC-4/5 improve startup time 10-15% is why I ask
and AOT compiling your lambda with direct linking may improve it more
you can enable direct linking with -Dclojure.compiler.direct-linking=true
@alexmiller: Will need more thorough testing, but right now averages are about the same with 1.8 RC5.
thx, probably dwarfed by other costs then
@martinklepsch: I saw Apex on HN, it looks very nice.