nx-cugraph needs to cache graph conversions for dispatched calls made within the context of other calls #4055
Labels
Story
Tracking issues as a story level - likely to exist within a single release.
Example: each call to
k_truss
can callisolates
3 times. Because each dispatched API call performs a conversion from the input NX graph to an internal PLC graph, a singlek_truss
call results in 4 identical conversions.This problem is causing excessive runtime, which not only defeats the purpose of using a backend but also forces devs to disable tests.
The current proposal to address this problem is to cache graph conversions made by the initial call, then re-use the cached converted graph object for subsequent calls. The cache is then cleared on exit of the initial call in order to prevent using conversions that are stale wrt the current state of the NX graph (ex. the NX graph had nodes or edges added or removed in between algo calls).
The text was updated successfully, but these errors were encountered: