QWQyyy opened a new issue, #5410: URL: https://github.com/apache/openwhisk/issues/5410
We hardware is 12vCPU and 32GB RAM K8s cluster, 3 nodes. My problem is that whenever I try to configure the container concurrency, such as setting the `-c` parameter to 2, 5, 10, 50, etc., but now it seems that OpenWhisk can only work correctly when the concurrency is 1. The specific performance is that the error of preheating the container directly occurs in the function call, as follows: ![image](https://github.com/apache/openwhisk/assets/54056797/5a742e31-7ba7-49ac-b555-430f0622a721) And the test program also shows a large number of timeouts, and this test runs normally when `-c` is configured as 1, I don’t know how to set up concurrency: ![image](https://github.com/apache/openwhisk/assets/54056797/01a5c321-eb84-4cd4-acba-45b975e252d7) I have configured value.yaml according to the suggestion you gave in the previous issue, as follows: ![image](https://github.com/apache/openwhisk/assets/54056797/c05418ef-1487-4907-8ac5-616bfb703bb1) At the same time, I also found an obvious problem, that is, when the number of preheated containers reaches 200, it is difficult to configure upwards, and there will be an error that the api gateway resource cannot be found. This is in the previous issue. My current difficulty is that it is difficult to use OpenWhisk to cope with a large amount of load. The data I currently get is only 200TPS, which is a very bad value. My function is very simple, just remotely calling a python3 runtime function of a redis database. Could you give me some advice? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org