Determining the leader is extremely cheap in the general case. It’s when
you have to exchange data (generally when that exchange involves
replication) that’s expensive. Or when you spin up 500 threads for 500
cheap operations. For the common use case, a very basic and long needed
feature in that regard is simple management. Rather then flood the system
at once with 500 replications, there needs to be a gate on how many
expensive operations like that can occur at once. Same with spinning up 500
threads. Maybe basic improvements like that won’t be the ideal end game for
a system that wants 100,000 lazy cores where most of them are rarely
active, but there is always going to be lots of tension trying to solve for
the typical use and a system like that.

Reply via email to