thankful-tailor-28399
08/11/2023, 10:27 AMThe worst case for FlytePropeller is workflows that have an extremely large fan-out. This is because FlytePropeller implements a greedy traversal algorithm…If we have workflows with this characteristic (for example, one workflow spans 2k dynamic tasks), is there a recommendation on how to scale? Otherwise we get alerts due to latency (which make sense for this specific wf), but it’s hard to isolate this scenario from other ones. For what I see in the docs, the suggestion is to limit the amount of parallel tasks
freezing-airport-6809
thankful-tailor-28399
08/11/2023, 1:46 PMthankful-tailor-28399
08/11/2023, 1:46 PMfreezing-airport-6809
freezing-airport-6809
thankful-tailor-28399
08/11/2023, 1:49 PMfreezing-airport-6809
thankful-tailor-28399
08/11/2023, 1:50 PMthankful-tailor-28399
08/11/2023, 1:50 PMfreezing-airport-6809
freezing-airport-6809