This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-01-15
Channels
- # admin-announcements (130)
- # alternate-reality (2)
- # aws (20)
- # beginners (49)
- # boot (1)
- # braid-chat (18)
- # cljsrn (54)
- # clojars (1)
- # clojure (70)
- # clojure-art (1)
- # clojure-japan (21)
- # clojure-miami (2)
- # clojure-my (7)
- # clojure-russia (60)
- # clojurescript (75)
- # community-development (12)
- # core-matrix (7)
- # cursive (23)
- # datomic (31)
- # dirac (2)
- # dunaj (3)
- # dysphemism (5)
- # editors-rus (1)
- # emacs (22)
- # events (9)
- # funcool (56)
- # hoplon (63)
- # human (1)
- # jobs (9)
- # ldnclj (7)
- # lein-figwheel (21)
- # leiningen (1)
- # off-topic (2)
- # om (61)
- # onyx (20)
- # other-lisps (2)
- # portland-or (1)
- # proton (26)
- # re-frame (27)
- # reagent (16)
- # ring-swagger (30)
- # spacemacs (6)
- # yada (5)
@clojuregeek Not seeing the issue myself, but in case I do… was it the expired credentials issue?
And since we’re on the topic of lambda… is anyone using Clojure for lambdas? I’ve been doing some tests on Clojure vs. ClojureScript, and the warm up hit on the Clojure lambdas is significant.
I think I remember something about Cursive licenses using lambdas with Clojure, but might be misremembering.
@ricardo: we use clojure for a few lambda functions, see: https://github.com/uswitch/lambada
@ricardo: warm up hit comes up everytime, only a (potential) problem on the first invocation
@ragge: Thanks, I actually wrote my clj tests with lambada. Main cause for concern is that the first call seems to take on average ~9s, and API Gateway times you out at 10s.
It’s calling to a couple external APIs which probably take 1-2s to complete. The rest should be its own time. What’s the usual memory you set up for your functions? I understand AWS scales the CPU accordingly, but haven’t seen a relation table anywhere.
That is… I haven’t seen a description for how the proportional scaling goes. In my test case the memory use is low, so it’s probably the CPU that’s affecting startup time.
Managed to get Datomic up and running on AWS ECS in a docker container. And I can connect to it from the EC2 host (so managed to get both host and alt-host set correctly, as well as the security settings of the AWS setup).
Small POC container showing the trick with the IP adresses: https://github.com/enterlab/docker-aws-ecs-env
@ricardo: yes i think it was, also I think my aws-cli was not set right which is what cljs-lambda uses