"蒋鹏程" <jiang.pengch...@navercorp.com> wrote on 08/31/2020 05:42:43 AM: > > Recently we are trying to migrate OpenWhisk from docker to K8S, but > faced some problems, and one of it is: the performance droped a > lot(the tps changed from thousands to dozens in our environment > during benchmarks) after migrating to K8S, and the reason we founded > is that all action containers will trying to fetch action logs from > K8S api server after `run` are finished, and these log requests > become very slow when there are logs of concurrent activations > comes, which in turn leads to a very low tps of activations.
Yes. Using the Kubernetes API to retrieve activation logs in the invoker is a performance disaster. Only usable for development/debugging. We do mention that in [1] and suggest some workarounds, but maybe this needs to be highlighted elsewhere. --dave [1] https://github.com/apache/openwhisk-deploy-kube/blob/master/docs/k8s-custom-build-cluster-scaleup.md
