Skip to main content

Dynamo Python Bindings

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

🚀 Quick Start

  1. Install uv: https://docs.astral.sh/uv/#getting-started
curl -LsSf https://astral.sh/uv/install.sh | sh
  1. Install protoc protobuf compiler: https://grpc.io/docs/protoc-installation/.

For example on an Ubuntu/Debian system:

apt install protobuf-compiler
  1. Setup a virtualenv
uv venv
source .venv/bin/activate
uv pip install 'maturin[patchelf]'
  1. Build and install dynamo wheel
maturin develop --uv

Run Examples

Prerequisite

See README.md.

Hello World Example

  1. Start 3 separate shells, and activate the virtual environment in each
source .venv/bin/activate
  1. In one shell (shell 1), run example server the instance-1
python3 ./examples/hello_world/server.py
  1. (Optional) In another shell (shell 2), run example the server instance-2
python3 ./examples/hello_world/server.py
  1. 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.

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distributions

If you're not sure about the file name format, learn more about wheel file names.

ai_dynamo_runtime-1.3.1-cp310-abi3-manylinux_2_28_x86_64.whl (47.1 MB view details)

Uploaded CPython 3.10+manylinux: glibc 2.28+ x86-64

ai_dynamo_runtime-1.3.1-cp310-abi3-manylinux_2_28_aarch64.whl (46.6 MB view details)

Uploaded CPython 3.10+manylinux: glibc 2.28+ ARM64

File details

Details for the file ai_dynamo_runtime-1.3.1-cp310-abi3-manylinux_2_28_x86_64.whl.

File metadata

File hashes

Hashes for ai_dynamo_runtime-1.3.1-cp310-abi3-manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 75ff5632372ad3278bcc3da6e2320e12f29fd663f93aba0db0127fac446e2a7b
MD5 f2579421682b1dce22ef2a75a5fb8b97
BLAKE2b-256 39b6cafb913e991359448c62c106aac71cf17c68d58a56dbb74620123e3e9363

See more details on using hashes here.

File details

Details for the file ai_dynamo_runtime-1.3.1-cp310-abi3-manylinux_2_28_aarch64.whl.

File metadata

File hashes

Hashes for ai_dynamo_runtime-1.3.1-cp310-abi3-manylinux_2_28_aarch64.whl
Algorithm Hash digest
SHA256 4d5c0a25b4d0bcaf2a88f9fd0fb5c9ea27261b6b0fcba94c15195bf208e4be00
MD5 432c4199b079e84bf108385a1ff83b83
BLAKE2b-256 fcd687b74be5572fc161e1ec0f4f6d74effea57ecf5661c73cb8cceb0b2f4114

See more details on using hashes here.

Release history Release notifications | RSS feed

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page