Scaling Temporal: The basics

What this post added

This post details a load testing process involving adjusting load, measuring performance via state transitions and request latency, and scaling Kubernetes resources and Temporal shard count. It highlights the importance of persistence backend as a bottleneck and the impact of shard count on lock contention and memory usage. It also discusses the trade-offs of increasing shard count, such as increased memory usage in History pods, and the current limitation of not being able to change shard count after cluster creation.