4 ms·
This advice might not be at all helpful, but anyway. Consider checking the following: - Number of CPUs. The number of CPUs is not CPU cores but Kubernetes mill
by Just1689 6y ago
This advice might not be at all helpful, but anyway.
Consider checking the following:
- Number of CPUs. The number of CPUs is not CPU cores but Kubernetes millicores. 1 vCPU on CR = 400m (4/10 of a CPU core).
- Background processes - not recommended [https://stackoverflow.com/questions/61154349/google-cloud-run-is-very-slow-vs-local-machine https://stackoverflow.com/questions/61154349/google-cloud-ru...]
- Container size on disk. Google Cloud is fast. However they need to cap the moving container images around as they can't use all the network capacity for moving a 400MB Docker image. If you're not already, use multi-stage builds with tiny final images.
- kircr 6y agoWhere do you get the info that 1 vCPU on CR = 400m? I would have expected 1 vCPU on CR = 1000m
- nikon 6y agoThis is not correct. > Limits and requests for CPU resources are measured in cpu units. One cpu, in Kubernetes, is equivalent to 1 vCPU/Core for cloud providers and 1 hyperthread on bare-metal Intel processors.