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
protocprotobuf 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.
6 maintainers
Metadata
6 maintainers
Release files for ai-dynamo-runtime 1.6.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ai_dynamo_runtime-1.6.0-cp310-abi3-manylinux_2_28_x86_64.whl | CPython 3.10 | abi3 | Linux glibc 2.28+ x86-64 | Details |
| ai_dynamo_runtime-1.6.0-cp310-abi3-manylinux_2_28_aarch64.whl | CPython 3.10 | abi3 | Linux glibc 2.28+ ARM64 | Details |
Total release size: 148.0 MB
Release files / ai_dynamo_runtime-1.6.0-cp310-abi3-manylinux_2_28_x86_64.whl
| Download URL | ai_dynamo_runtime-1.6.0-cp310-abi3-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 74.7 MB |
| Tags | CPython 3.10 Linux glibc 2.28+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
c70a3f0ed1a756fc199c44c1558314dd44cdab82233849d0b1e53f4f41267f0b
|
|
BLAKE2b-256 checksum How to use checksums |
273da037456129fc9bb99f2857839502feb8345c2462b9ed0b5fb5b8dd249199
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Release files / ai_dynamo_runtime-1.6.0-cp310-abi3-manylinux_2_28_aarch64.whl
| Download URL | ai_dynamo_runtime-1.6.0-cp310-abi3-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 73.3 MB |
| Tags | CPython 3.10 Linux glibc 2.28+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
eb38cedb4802ca3f86b15341ce9527dbbb4bc633e6249bd31655ecc77cdb3f00
|
|
BLAKE2b-256 checksum How to use checksums |
2aa21a149ce286153f0cbcd95ab6c4b74d662619b4f17bd2e0070971cfdfb45d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Security for ai-dynamo-runtime 1.6.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
