2020-05-13 13:53:49 UTC - Rodric Rabbah: my kids class will be joining us on zoom :smile: https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1589378029274800 ---- 2020-05-13 13:54:21 UTC - Rodric Rabbah: if you’re attending the openwhisk community call, there is a password on the account now https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1589378061275400 ---- 2020-05-13 13:55:13 UTC - Rodric Rabbah: do me or @Dave Grove or @Matt Rutkowski for password if you need it https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1589378113275900 ---- 2020-05-13 13:56:16 UTC - Dave Grove: Starting in 5 minutes: <http://zoom.us/my/asfopenwhisk> https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1589378176276500 ---- 2020-05-13 20:55:06 UTC - Bilal: Yes it was caused by my ES, I changed to the bitnami chart and that seemed to have solved the issue https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1589403306276700?thread_ts=1588354797.201900&cid=C3TPCAQG1 ---- 2020-05-13 23:23:29 UTC - Sam: Hi~ I’m running a benchmark on OpenWhisk which sends a burst of concurrent requests. Now at the concurrency of 100 requests, I’m facing the problem of timeout errors. I’ve increased the limits to `200` in the cluster yaml file. How the test works is that it deploys a function, sends requests, and removes the function. After the test, I checked pods, and it seems that a lot of pods were still initializing. How should I make it to be able to handle the loads? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1589412209280300?thread_ts=1589412209.280300&cid=C3TPCAQG1 ----
