portkey

Portkey: from REPL to Serverless in one call
viesti 2018-03-23T14:38:45.000165Z

hum

viesti 2018-03-23T14:39:07.000096Z

> 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.

viesti 2018-03-23T14:40:53.000435Z

Thinking that when we get to implementing delta redeploy (https://github.com/portkey-cloud/portkey/issues/10) we can cache precompiled classes in /tmp

viesti 2018-03-23T14:41:07.000107Z

and fetch only newly compiled classes

viesti 2018-03-23T14:41:55.000285Z

hmm, although /tmp is probably ec2 dependend

viesti 2018-03-23T14:42:18.000051Z

if a new invocation ends up creating a process on a separate machine, cache won’t be there

viesti 2018-03-23T14:42:27.000090Z

hmm

viesti 2018-03-23T14:42:51.000805Z

another thing:

viesti 2018-03-23T14:42:52.000206Z

> 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.

viesti 2018-03-23T14:43:09.000206Z

this might mean that this could be done on the background…

viesti 2018-03-23T14:43:47.000213Z

wonder how billing goes in that situation…

viesti 2018-03-23T14:44:54.000098Z

hum, I think we/you (don’t remember author of the idea) had such background loading idea

viesti 2018-03-23T14:45:03.000731Z

even inside the lambda process

cgrand 2018-03-23T14:45:07.000049Z

On bg process, I think it’s clear: when the main processing halts they are frozen

viesti 2018-03-23T14:45:17.000666Z

hmm, might be so

viesti 2018-03-23T14:45:33.000494Z

since

viesti 2018-03-23T14:45:35.000338Z

resume if AWS Lambda chooses to reuse the Execution Context.

cgrand 2018-03-23T14:45:40.000337Z

(a week or so ago I researched bout them)

viesti 2018-03-23T14:45:42.000167Z

stated by that

cgrand 2018-03-23T14:46:28.000650Z

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

viesti 2018-03-23T14:47:12.000556Z

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

viesti 2018-03-23T14:47:21.000248Z

right

cgrand 2018-03-23T14:47:33.000511Z

delta redeploys are two fold: • upload less • do a “soft” redeploy

viesti 2018-03-23T14:47:41.000660Z

yes

viesti 2018-03-23T14:49:21.000282Z

soft would be for 5min, but thinking that if same compute instance is reused, jvm might be warm too

viesti 2018-03-23T15:07:33.000043Z

how's the idea on instrumenting java.security factories?

cgrand 2018-03-23T15:08:02.000110Z

too busy to implement it

viesti 2018-03-23T15:09:51.000367Z

if I'd be able to infuse the weights of your neural net to be able to implement/help in implementing :)

cgrand 2018-03-23T15:10:19.000654Z

we don’t have an issue open for these cryptos?

viesti 2018-03-23T15:11:47.000244Z

aah, that I can do

viesti 2018-03-23T15:12:06.000386Z

with less training on my net

viesti 2018-03-23T15:13:06.000632Z

there's a test though, I'll link to it

viesti 2018-03-23T15:13:53.000532Z

had in mind to do a bot that watches CircleCI build status (since can't add CircleCI integration to Slack)

2018-03-23T16:18:20.000372Z

2018-03-23T16:31:15.000593Z

2018-03-23T16:35:21.000518Z

2018-03-23T16:51:50.000215Z

2018-03-23T17:57:55.000134Z

2018-03-23T18:07:23.000178Z