alexeyrybak

Copying the summary here.

Redis-benchmark, GET commands 64 clients, bare metal Xeon Gold 6312U 24/48vCPU, 128G; 10M keys DB size, 256 bytes each.

Summary: - Redis does scale! and performance is fine on low-cores infra - Valkey scales much better with significantly lower latency - Both have limitations due to single-main-thread architecture (having>8 vcpus doesn't make much sense - use several services per box or cluster mode)

"The most important" phrase is misleading, I agree. The idea was to underline the importance of cpu resources on apps cluster but not to state it's the most important thing, the main, the one, always. You are correct.

Pardon, are you sure there was anything about being "equally balanced"? Why 100 databases lead to 100 app servers? I'm afraid the key point is missed: in a balanced system, when input load increases, all parts should slow down all together. Means you just need to have a "proper" proportion of resources in various parts of the system. No need to have 100 apps if your MySQL cluster dies only at 25% cpu load on the apps cluster. This might just indicate you better have 25 app servers vs 100 databases, and spend the rest of money proportionally on both clusters (assuming you only have apps and databases). And a good balance also doesnt mean you have perfectly designed or optimized system. These are different things.

Hey, we will publish English article early next week, but you can just scroll down to the usage graphs. Thanks!