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
In https://github.com/yb01/arktos/wiki/730-test, for Test case - 500K nodes / 2 regions / 20 schedulers / 25K nodes per scheduler, when one resource region manager simulator is in AWS region us-west-1, another resource region manager simulator, service-api, all schedulers are in AWS region us-west-2,
The percentages of "Number of nodes watch prolonged than 1s" on all schedulers reach 20-40% high dramatically.
It is wired.
The text was updated successfully, but these errors were encountered:
q131172019
changed the title
One region simulator in different AWS region from that of service-api, schedulers and another region simulator causes high percentage of "Number of nodes watch prolonged than 1s"
One region simulator in different AWS region from that of service-api, schedulers and another region simulator causes high percentage of "Number of nodes watch prolonged than 1s" on all schedulers
Jul 13, 2022
keep it for 930 now. likely move to 1230 as perf goal. --- RP down data change
yb01
changed the title
One region simulator in different AWS region from that of service-api, schedulers and another region simulator causes high percentage of "Number of nodes watch prolonged than 1s" on all schedulers
Improve end to end watch node event latency -- currently prolonged ( > 1 sec ) is high
Aug 11, 2022
In https://github.com/yb01/arktos/wiki/730-test, for Test case - 500K nodes / 2 regions / 20 schedulers / 25K nodes per scheduler, when one resource region manager simulator is in AWS region us-west-1, another resource region manager simulator, service-api, all schedulers are in AWS region us-west-2,
The percentages of "Number of nodes watch prolonged than 1s" on all schedulers reach 20-40% high dramatically.
It is wired.
The text was updated successfully, but these errors were encountered: