This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-12-10
Channels
- # admin-announcements (32)
- # announcements (4)
- # aws (25)
- # beginners (296)
- # boot (1)
- # cider (87)
- # clara (16)
- # cljs-dev (7)
- # cljsrn (41)
- # clojure (121)
- # clojure-art (26)
- # clojure-japan (4)
- # clojure-miami (190)
- # clojure-russia (168)
- # clojure-sg (3)
- # clojure-sweden (13)
- # clojurescript (138)
- # clojurex (7)
- # cursive (98)
- # data-science (2)
- # datomic (129)
- # devcards (10)
- # editors (5)
- # funcool (1)
- # hoplon (31)
- # jobs (1)
- # ldnclj (4)
- # lein-figwheel (3)
- # off-topic (2)
- # om (213)
- # onyx (33)
- # parinfer (7)
- # portland-or (1)
- # re-frame (19)
- # reagent (2)
- # ring-swagger (27)
- # slack-help (3)
@cfleming: btw, did you end up using lambda for the license buying stuff?
@martinklepsch: Yeah, I did. It was a mixture of agony and ecstasy
Haven't used API gateway yet but everyone seems to hate it so already looking forward lol
This has been asked before I think but some more anecdotal knowledge would be interesting: how is startup time? @cfleming
(assuming you used Clojure not ClojureScript)
@martinklepsch: Sorry, fighting a few release-related fires, will get whisky for war tales in a bit.
sure, good luck đź‘Ť congrats again, must be a really big day for you
massive. congrats cfleming !
Thanks guys! It’s been a ton of work to get here, I can’t wait to work on functionality again!
@martinklepsch: I don’t actually know about instance startup time, it’s actually fairly difficult to measure. You do get a total elapsed time in CloudWatch, so if you create a simple Java lambda that doesn’t do anything you could probably test it.
That’s not my main problem though. The biggest pain point is that API gateway has a hard 10-sec timeout for Lambda backends. That sounds like a lot, but I’m getting a lot of timeouts when I access AWS services for the first time. Creating a DynamoDB client, finding a table and loading a single record out of it takes around 7.2 seconds when the instance is cold.
Once it’s warmed up a bit (interestingly, this isn’t true for the second request, more like the third or fourth) it starts to get a lot faster.
that sucks
It’s actually not a great fit for occasional requests, which is daft - that seems like its ideal use case.
I actually put Dynamo in the mix to make the lambda idempotent because I was already seeing long timeouts for other services I use (KMS), but they’re faster once Dynamo is loaded first, so it must be some connection to AWS in general that’s taking the time.
not good for occasional web requests, but we're using it as a timer and it's great in that role