A and B are what I'd pick here. Scaling worker count or boosting instance type directly tackles CPU starvation in Dataflow. The buffer options (D, E) deal more with throughput spikes or persistent queueing, not pure compute limits. Pretty sure this is the intent, but open if anyone disagrees.
Had something like this in a mock before. Isn’t increasing max workers (A) and using bigger instances (B) the straightforward way to deal with CPU bottlenecks? Adding buffers like D or E sounds more for handling message surges, not compute limits. Agree?
I don't think D or E make sense here, since those buffer options just add complexity and won't solve the CPU bottleneck. A and B are way more direct, either scale out or use beefier machines. C's tricky but violates EU data residency, so that's probably a trap. Agree?
