-
Notifications
You must be signed in to change notification settings - Fork 6.8k
2.0 migration guide? #20109
Comments
Thanks for bringing this up. Yes I think we definitely need a migration guide. |
Ok I went looking for how the python wrapper (symbol.py and executor.py) got adapted to work with the cached op API and I'm starting to get a feeling of the current scenario. Some questions:
|
Hi @matteosal. Thanks for looking into this.
Yes
Not yet, though this is indeed a useful functionality.
When
These are flags for bulk execution. When bulk execution happens with |
Another question: in v1.x it was possible to query executors for their allocated memory:
Is there a way to get the equivalent of the line "Total 346 MB allocated" with cached ops? |
Not yet. It would be great to add back that feature |
More on the cached op flags:
Since this is an option to set, I guess there is a downside to running a large number of operators in one call. What is it? Increased memory usage? Is there a similar tradeoff for |
Is there a resource or set of resources for migrating a project to v2.0? I am specifically interesed to the C API. I have checked #17676 but it's not very specific apart from the
*Ex
functions removal/renaming.For example everything related to executors, on which our code relies heavily, is gone in v2.0. This PR #18598 mentions "we will use cached_op_create/invoke in favor of graph executor c APIs" but I couldn't find detailed information on how to migrate code using the executor API to cached ops.
The text was updated successfully, but these errors were encountered: