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
@shrek
Hi, Is it possible to run FlexFlow on a real model but simulated devices and topology ? The result of this would be the "best strategy + device mapping". Some older code suggest that in the past this was possible. But the current code and tests seem to require real devices.
I am thinking of a refactor where the unity algorithms work on a device/topology abstraction (with operation costs, operation memory usage and communication costs abstracted). This would abstract the algorithms from the devices and the distributed runtime.
@shrek
thanks, let me try these out. I havent looked at the refactor branches yet, but I am thinking an ideal refactor would abstract the algorithms, the devices+topology and the distributed runtime into orthogonal and pluggable components.
I would like to contribute towards this effort. I found a bunch of memory leaks (using valgrind) - perhaps fixing those can be my first contribution.
@lockshaw @shrek Contributions are always welcome 🙂. If the memory leaks are in the simulator, then they will likely still be around after Repo Refactor #622 and so a fix would be much appreciated. If they are in other parts of the code, you may want to check out Repo Refactor #622 to see if that change fixes them.
The text was updated successfully, but these errors were encountered:
Moved from #675
The text was updated successfully, but these errors were encountered: