In reference to issue https://github.com/dagster-io/dagster/issues/3463.
We re-compute the execution plan at every step for the purpose of computing version information. This diff hides that computation behind an experimental tag s.t. no normal runs will have version information computed.
I verified that the version computation code paths were never hit after this change in the affected tests. This change results in a >50% improvement in the speed of test_composites.py::test_composite_basic_execution.
Details
Details
Unit tests. Verified manually that versioning code paths were never hit on a normal run.
Before change: 22s for test_composites.py::test_composite_basic_execution.
After change: 9s for test_composites.py::test_composite_basic_execution.
Diff Detail
Diff Detail
- Repository
- R1 dagster
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Comment Actions
Since you already have the profiling set up, do you have a notion what the hot paths are for the remaining 9 seconds?
Comment Actions
I didn't get too great of a picture with the work I did for this, but I'll investigate further and follow up.