Grapgflow is not a parallel flow, actually just a concurrent flow #6488
prety-good
started this conversation in
General
Replies: 1 comment 1 reply
-
@prety-good thanks for your issue. It is correct the GraphFlow currently executes nodes sequentially. The API is experimental so consider it not fully baked. There are several things under development including support for functional conditions in edges. If you are interested to discuss implementation, you can join Discord channel: https://discord.com/channels/1313229474107756584/1341892471084548198 for contributors. Converting this to a discussion. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What happened?
Describe the bug
I am glad to see the launch of graphflow function,but after my attempts, Grapgflow is not a parallel flow, it is actually just concurrent. It just executes the agents that need to be parallel sequentially.
To Reproduce
In the graphflow function, I create 3 test_agent to parallelly run:
While in my code, I use the
asyncio.gather
to parallelly run, just like:Expected behavior
In the parallelism implemented by graphflow, the outputs of different agents are independent and appear to be executed sequentially.
In my code, the outputs of different agents are mixed and the running speed is twice as fast as graphflow.
Is there something wrong with my implementation, or is graphflow just a concurrent method and does not support parallelism?
Which packages was the bug in?
Python AgentChat (autogen-agentchat>=0.4.0)
AutoGen library version.
Python 0.5.6
Other library version.
No response
Model used
No response
Model provider
None
Other model provider
No response
Python version
3.10
.NET version
None
Operating system
MacOS
Beta Was this translation helpful? Give feedback.
All reactions