PrefectHQ
prefect
BlogDocsChangelog

Allow `flow.sumbit` to be non-blocking for some infrastructure types

#17992Merged
Comparing
worker-run-no-wait
(
3aea9bc
) with
main
(
efd760e
)
CodSpeed Performance Gauge
0%
Untouched
2
Ignored
6

Benchmarks

Passed

bench_task_decorator
benches/bench_tasks.py
CodSpeed Performance Gauge
0%
448.9 µs449.2 µs
bench_import_prefect_flow
benches/bench_import.py
CodSpeed Performance Gauge
0%
1.2 s1.2 s

Ignored

bench_flow_call[options0]
benches/bench_flows.py
Ignored
CodSpeed Performance Gauge
+1%
164.1 ms162.9 ms
bench_task_call
benches/bench_tasks.py
Ignored
CodSpeed Performance Gauge
-8%
159.2 ms173.2 ms
bench_task_submit
benches/bench_tasks.py
Ignored
CodSpeed Performance Gauge
+23%
5.7 ms4.6 ms
bench_import_prefect
benches/bench_import.py
Ignored
CodSpeed Performance Gauge
0%
2.7 ms2.7 ms
bench_flow_call[options1]
benches/bench_flows.py
Ignored
CodSpeed Performance Gauge
0%
106 ms105.7 ms
bench_flow_decorator
benches/bench_flows.py
Ignored
CodSpeed Performance Gauge
-7%
4.1 ms4.5 ms

Commits

Click on a commit to change the comparison range
Base
main
efd760e
-0.33%
Add `initiate_run` method to `BaseWorker` The `initiate_run` method is a new method that is used to create infrastructure for a flow run, but not watch the created infrastructure or wait for the flow run to complete.
1840dd5
5 months ago
by desertaxle
+0.15%
Fix K8s integrations tests after uv step update
f15c467
5 months ago
by desertaxle
+0.33%
Update Vertex AI worker to allow initiating a flow run without waiting for completion
e95a8c9
5 months ago
by desertaxle
-0.26%
Make `initiate_run` a "private" method
3aea9bc
5 months ago
by desertaxle
© 2025 CodSpeed Technology
Home Terms Privacy Docs