This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-03-15
Channels
- # aatree (1)
- # atlanta-clojurians (3)
- # beginners (112)
- # boot (4)
- # boot-dev (1)
- # bristol-clojurians (1)
- # cider (55)
- # cljs-dev (23)
- # cljsjs (1)
- # cljsrn (7)
- # clojars (24)
- # clojure (84)
- # clojure-brasil (1)
- # clojure-china (1)
- # clojure-italy (27)
- # clojure-norway (17)
- # clojure-romania (1)
- # clojure-spec (109)
- # clojure-uk (92)
- # clojurescript (94)
- # community-development (1)
- # core-matrix (1)
- # cursive (12)
- # datascript (1)
- # datomic (23)
- # figwheel (1)
- # fulcro (17)
- # hoplon (11)
- # jobs-discuss (3)
- # keechma (6)
- # lein-figwheel (4)
- # leiningen (79)
- # lumo (32)
- # mount (42)
- # off-topic (22)
- # onyx (13)
- # parinfer (30)
- # portkey (47)
- # powderkeg (1)
- # programming-beginners (24)
- # protorepl (3)
- # re-frame (16)
- # reagent (100)
- # ring-swagger (7)
- # shadow-cljs (134)
- # spacemacs (3)
- # sql (1)
- # tools-deps (48)
- # uncomplicate (1)
- # unrepl (14)
- # yada (1)
at the AWS day the amazon lot said to use cloudwatch to ping as a workaround which was a bit eek
If in each lambda we probabilisticly determine to invoke the lambda again (just for warmup) then we dynamically warm up more instances.
@viesti @dominicm @alex.lynham am I nut?
so haven’t done investigation, but there were some posts that every 4hours the cluster reboots
yeah they randomly bring the lambda instances down every once in a while
so you have cold starts from not being used & cold starts from instances being cycled
if your lambda is active enough it’s deployed on several containers so on cycling you lose only some of your caapacity, not all
very true
I guess as long as there's at least a small pool at any given time you should be golden
when we used to shuffle around v large volumes in amazon we had to warm things as part of a deployment step so sometimes hacks are needed
¯\(ツ)/¯
I’m looking for a reference for this statement > The container is not used for a second invocation until the first one finishes.
I have written a crude simulator: https://gist.github.com/cgrand/8a57d5761d2c5c5ab5dbec25d5d0c823
under constant load (which is the best case for Lambda), the number of perceived cold starts would be almost halved with probabilistic warmup
hmm, at which point does it cost more to keep warm lambdas then to run an on-demand ec2 (cost dependa on instance type)
When I suggested probabilistic warmup it was to ensure there was always a buffer of ready containers to diminish latency on activity bursts.
> work and integration There is? ASGs are fairly well explored. You set them to a minimum of X and you're good to go? Maybe I'm used to the convenience of terraforn/cloudformation managing that stuff
hmh, didn’t figure out how to put documentation key into shape: https://github.com/aws/aws-sdk-java/blob/master/aws-java-sdk-models/src/main/resources/models/elasticfilesystem-2015-02-01-model.json#L28
portkey.awsgen> (generate-files!)
generating “appsync” “2017-07-25"
generating “events” “2015-10-07"
skipping portkey.aws.events.-2015-10-07 protocol “json”
generating “elasticfilesystem” “2015-02-01”
generating “serverlessrepo” “2017-09-08”
ExceptionInfo In: [1 1 “SourceCodeUrl” 1 1 0] val: “locationName” fails at: [:members 1 1 :querystringmap :shape 0] predicate: #{“shape”}