You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Auto-scaling up/down actor groups based on the incoming traffic. And the perfect place for a getting a better scalability and performance cases could be the bastion executor.
Describe the solution you'd like
An existing solution (on which I'm currently working on) based on adding a Resizer instance to the Children. So it could time-to-time make checks and scalin up/down based on the aggregated statistics from actors.
This solution based on the new approach where resizers could be a part of back-pressure cases. And when back-pressure cases happen, resizer could try create a new actor and rebalance incoming data/packet/request to this actor instead. But in the case if it can't do it (due reaching the limits), we could just rollback to the default back-pressure logic.
But the single nuance here is to how to store parent / child id as the part of the context, so the resizer could call or pass a message to the certain node.
Describe alternatives you've considered
N/A
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Auto-scaling up/down actor groups based on the incoming traffic. And the perfect place for a getting a better scalability and performance cases could be the bastion executor.
Describe the solution you'd like
An existing solution (on which I'm currently working on) based on adding a Resizer instance to the Children. So it could time-to-time make checks and scalin up/down based on the aggregated statistics from actors.
This solution based on the new approach where resizers could be a part of back-pressure cases. And when back-pressure cases happen, resizer could try create a new actor and rebalance incoming data/packet/request to this actor instead. But in the case if it can't do it (due reaching the limits), we could just rollback to the default back-pressure logic.
But the single nuance here is to how to store parent / child id as the part of the context, so the resizer could call or pass a message to the certain node.
Describe alternatives you've considered
N/A
The text was updated successfully, but these errors were encountered: