From 1c96e284275a1685a3459b4479033e6ccf26d308 Mon Sep 17 00:00:00 2001 From: Your Name Date: Mon, 16 Sep 2024 23:25:23 -0400 Subject: [PATCH] [DOCS][CLEANUP] --- docs/swarms/concept/how_to_choose_swarms.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/swarms/concept/how_to_choose_swarms.md b/docs/swarms/concept/how_to_choose_swarms.md index dc1415ca..167deb73 100644 --- a/docs/swarms/concept/how_to_choose_swarms.md +++ b/docs/swarms/concept/how_to_choose_swarms.md @@ -129,9 +129,11 @@ When dealing with massive-scale data or agent outputs that need to be stored and ## Final Thoughts The choice of swarm depends on: + 1. **Nature of the task**: Whether it's sequential or parallel. + 2. **Problem complexity**: Simple problems might benefit from RoundRobin, while complex ones may need GraphWorkflow or Mixture of Agents. + 3. **Scale of execution**: For large-scale tasks, Swarms like SpreadsheetSwarm or MajorityVoting provide scalability with structured outputs. When integrating agents in a business workflow, it's crucial to balance task complexity, agent capabilities, and scalability to ensure the optimal swarm architecture. -