This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-01-16
Channels
- # admin-announcements (94)
- # aws (6)
- # beginners (8)
- # boot (303)
- # cider (5)
- # cljsrn (25)
- # clojure (82)
- # clojure-art (28)
- # clojure-chicago (2)
- # clojure-dev (2)
- # clojure-france (1)
- # clojure-japan (1)
- # clojure-my (1)
- # clojure-russia (78)
- # clojurescript (21)
- # clojurex (3)
- # dirac (1)
- # events (3)
- # funcool (5)
- # hoplon (12)
- # jobs (1)
- # ldnclj (2)
- # off-topic (49)
- # om (207)
- # proton (3)
- # re-frame (24)
- # reagent (45)
- # spacemacs (1)
- # yada (48)
@ricardo: Cursive does indeed use Lambda for licence generation. I see something similar to what you’re seeing, the first invocation in a while takes ~7.2 seconds to access dynamo.
@ricardo: But I put Dynamo in to fix the fact that accessing some other service (probably KMS) caused timeouts - I suspect it’s the first access to an AWS service.
This doesn’t have anything to do with instance startup time, it’s accessing AWS services.
Thanks @cfleming. This is a pretty minimal example, since I wanted to do a basic start up time test that still called out to APIs of Clojure lambdas vs. ClojureScript. It does look like increasing the memory (and CPU along with it) is a workaround to improve the start up time, though.