This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-03-23
Channels
- # bangalore-clj (5)
- # beginners (136)
- # boot (1)
- # bristol-clojurians (6)
- # cider (46)
- # cljs-dev (172)
- # cljsrn (35)
- # clojure (82)
- # clojure-china (2)
- # clojure-dev (9)
- # clojure-dusseldorf (1)
- # clojure-finland (15)
- # clojure-italy (54)
- # clojure-norway (4)
- # clojure-russia (6)
- # clojure-spec (19)
- # clojure-uk (61)
- # clojurebridge (1)
- # clojurescript (55)
- # community-development (23)
- # cursive (7)
- # datomic (19)
- # emacs (10)
- # events (4)
- # fulcro (108)
- # graphql (7)
- # hoplon (1)
- # leiningen (7)
- # lumo (14)
- # off-topic (68)
- # onyx (23)
- # parinfer (8)
- # portkey (40)
- # precept (11)
- # re-frame (5)
- # reagent (40)
- # ring-swagger (5)
- # shadow-cljs (58)
- # specter (5)
- # tools-deps (37)
- # unrepl (13)
- # vim (9)
- # yada (12)
> Each Execution Context provides 500MB of additional disk space in the /tmp directory. The directory content remains when the Execution Context is frozen, providing transient cache that can be used for multiple invocations.
Thinking that when we get to implementing delta redeploy (https://github.com/portkey-cloud/portkey/issues/10) we can cache precompiled classes in /tmp
if a new invocation ends up creating a process on a separate machine, cache won’t be there
> Background processes or callbacks initiated by your Lambda function that did not complete when the function ended resume if AWS Lambda chooses to reuse the Execution Context. You should make sure any background processes or callbacks (in case of Node.js) in your code are complete before the code exits.
hum, I think we/you (don’t remember author of the idea) had such background loading idea
so basically if you have a heavy bg process it’s going to slow down your handler and thus you’ll be billed for the whole combined esexcution time that’s all
apropo, was working on reading models from aws-java-sdk-models
for aws-clj-sdk
, but got bogged down on some new api, thinking about just skipping those that need changes to be supported
soft would be for 5min, but thinking that if same compute instance is reused, jvm might be warm too
if I'd be able to infuse the weights of your neural net to be able to implement/help in implementing :)