2020-12-13 03:12:32 UTC - Matt Welke: I'm trying to get a good understand of the different options I have for deploying code as an action. After reading the docs, including the sections on custom runtimes and binaries, I've come to the following conclusion:
If I have code in an interpreted language, like Node.js, I can deploy using: - A traditional, non-ActionLoop runtime image (considered high performance) - An ActionLoop runtime image (considered high performance) - A custom runtime image I make, with self contained code, I host an HTTP server on port 8080 with /init and /run (considered high performance) If I have code in a compiled language, like Go, I can deploy using: - A traditional, non-ActionLoop runtime image (considered high performance) - An ActionLoop runtime image (considered high performance) - A custom runtime image I make, with self contained code, I host an HTTP server on port 8080 with /init and /run (considered high performance) - The Docker runtime (aka docker-skeleton) with self contained binary (considered low performance, because the binary is ran as a new process for each action invoke) Can anyone confirm this for me? white_check_mark : Rodric Rabbah https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1607829152403100?thread_ts=1607829152.403100&cid=C3TPCAQG1 ---- 2020-12-13 04:30:04 UTC - Rodric Rabbah: this is correct. Note that node.js doesn’t implement the action loop protocol (@Michele Sciabarra found the performance is the same for node with and without it) https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1607833804403300?thread_ts=1607829152.403100&cid=C3TPCAQG1 ---- 2020-12-13 06:14:56 UTC - Michele Sciabarra: yes there is the benchmarch I did some time ago <https://sciabarracom.github.io/incubator-openwhisk-runtime-actionloop/> +1 : Dominic Kim https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1607840096403600?thread_ts=1607829152.403100&cid=C3TPCAQG1 ----
