Dynamo Python Bindings

Python bindings for the Dynamo runtime system, enabling distributed computing capabilities for machine learning workloads.

🚀 Quick Start

Install uv: https://docs.astral.sh/uv/#getting-started

curl -LsSf https://astral.sh/uv/install.sh | sh

Install protoc protobuf compiler: https://grpc.io/docs/protoc-installation/.

For example on an Ubuntu/Debian system:

apt install protobuf-compiler

Setup a virtualenv

uv venv
source .venv/bin/activate
uv pip install 'maturin[patchelf]'

Build and install dynamo wheel

maturin develop --uv

Run Examples

Prerequisite

See README.md.

Hello World Example

Start 3 separate shells, and activate the virtual environment in each

source .venv/bin/activate

In one shell (shell 1), run example server the instance-1

python3 ./examples/hello_world/server.py

(Optional) In another shell (shell 2), run example the server instance-2

python3 ./examples/hello_world/server.py

In the last shell (shell 3), run the example client:

python3 ./examples/hello_world/client.py

If you run the example client in rapid succession, and you started more than one server instance above, you should see the requests from the client being distributed across the server instances in each server's output. If only one server instance is started, you should see the requests go to that server each time.

Performance

The performance impacts of synchronizing the Python and Rust async runtimes is a critical consideration when optimizing the performance of a highly concurrent and parallel distributed system.

The Python GIL is a global critical section and is ultimately the death of parallelism. To compound that, when Rust async futures become ready, accessing the GIL on those async event loop needs to be considered carefully. Under high load, accessing the GIL or performing CPU intensive tasks on on the event loop threads can starve out other async tasks for CPU resources. However, performing a tokio::task::spawn_blocking is not without overheads as well.

If bouncing many small message back-and-forth between the Python and Rust event loops where Rust requires GIL access, this is pattern where moving the code from Python to Rust will give you significant gains.

Metadata

Release files for ai-dynamo-runtime 1.6.0.dev20261004

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distributions (wheels)

Table of built distributions (wheels) for ai-dynamo-runtime 1.6.0.dev20261004
File	Interpreter	ABI	Platform	Reset
ai_dynamo_runtime-1.6.0.dev20261004-cp310-abi3-manylinux_2_28_x86_64.whl 71.2 MB Oct 4, 2026	CPython 3.10	abi3	Linux glibc 2.28+ x86-64	Details
ai_dynamo_runtime-1.6.0.dev20261004-cp310-abi3-manylinux_2_28_aarch64.whl 69.7 MB Oct 4, 2026	CPython 3.10	abi3	Linux glibc 2.28+ ARM64	Details

Total release size: 140.9 MB

Release files / ai_dynamo_runtime-1.6.0.dev20261004-cp310-abi3-manylinux_2_28_x86_64.whl

Download URL	ai_dynamo_runtime-1.6.0.dev20261004-cp310-abi3-manylinux_2_28_x86_64.whl
Size	71.2 MB
Tags	CPython 3.10 Linux glibc 2.28+ x86-64 abi3
SHA-256 checksum How to use checksums	`115770f7d776d28008d91dfc8e884752e1de787d674352f0dc160473c65310f8`
BLAKE2b-256 checksum How to use checksums	`416d49c6f41e9eccfe964e0f51cc3fe72007303fbd4aa8a5cdfea8c3ca81ac5c`
Upload date	Oct 4, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/7.0.0 CPython/3.14.7`

Release files / ai_dynamo_runtime-1.6.0.dev20261004-cp310-abi3-manylinux_2_28_aarch64.whl

Download URL	ai_dynamo_runtime-1.6.0.dev20261004-cp310-abi3-manylinux_2_28_aarch64.whl
Size	69.7 MB
Tags	CPython 3.10 Linux glibc 2.28+ ARM64 abi3
SHA-256 checksum How to use checksums	`fefeb3506cfb2c59de59d59525c63fdde83449f662ef17e6e166c33852746601`
BLAKE2b-256 checksum How to use checksums	`00d444270638d474f574e95497ef3869cd883e1f23a0128c0efd07aa796c05f2`
Upload date	Oct 4, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/7.0.0 CPython/3.14.7`