Currently, buildCache is not persisted between execution runs. This results in the entire graph being executed, with potentially long running checks. While this ensures that the graph execution is always consistent, it can be slow to execute deeply nested graphs.
If we persist the buildCache, and have an associated policy to refresh it either on demand OR on a time basis, it can avoid potentially expensive checks.
Currently,
buildCacheis not persisted between execution runs. This results in the entire graph being executed, with potentially long running checks. While this ensures that the graph execution is always consistent, it can be slow to execute deeply nested graphs.If we persist the
buildCache, and have an associated policy to refresh it either on demand OR on a time basis, it can avoid potentially expensive checks.