@G_W_Albrecht let me rephrase 🙂
Dynamic Split is designed to overcome an ineffectiveness of static SND/FWK split in the conditions of fast changing traffic. The challenge raises from the two-fold:
- You use a single appliance running Active.
- SND/FWK split is set manually and cannot be changed without reboot in 2.6 kernel environment.
Dynamic Split then allows avoiding situation where either SNDs or FWKs are overwhelmed, by balancing CPU load with changing roles, as needed.
Maestro can leverage the whole stack of appliances, effectively having SND/FWK numbers multiplied by the amount of available machines. Balances processing on two layers: per machine with SXL and PXL, between SDKs and FWKs, and between the different physical boxes.
Thank means, it is much less likely that we face the classic DS challenge in Maestro environment, just because we have many more CPUs for both roles.
This is pretty clear for you, I believe, so I am just writing it down for other readers of this thread.
Now, when it comes to heavy connections, a single connection cannot be split between several CPUs anyway, so it remains a challenge. AFAIK, R&D is trying to address a situation when multiple heavy connections could be set on different cores, but I do not have details or ETA to share at this point.
