IssueTracker

What you would like to accomplish:

Upgrading Python SDK version to 2.5.x, or the latest, with Runner V2 enabled succeeds without performance issues for all pipelines. Although V2 often brings cost and performance improvements relative to V1, for some pipeline configurations it can cause regressions (e.g. OOM issue).

If applicable, reasons why alternative solutions are not sufficient:

Refactoring custom code is sometimes difficult due to dependencies.

Other information (workarounds you have tried, documentation consulted, etc):

• Troubleshooting pipelines is the appropriate landing page for recommendations on troubleshooting pipeline issues.
• For OOMs please consult the OOM troubleshooting guide which has recommendations on how to diagnose memory issues and/or mitigate the memory demands of the pipeline (such as decreasing the number of worker threads).
• Optimizing algorithms used during processing is generally the most effective first approach if possible.
• As a last resort, disabling Runner V2 with --experiments=disable_runner_v2 may unblock execution if the performance issues do not occur on V1 but should not be a permanent solution in most cases.