Compute Backends
DynexConfig selects which hardware handles your computation. The primary backend for all production workloads is GPU — Dynex’s own neuromorphic computing chips operated across a distributed GPU network worldwide.
Overview
| Backend | Hardware | Use case |
|---|---|---|
GPU | Dynex neuromorphic GPU chips | Production — the primary Dynex backend |
QPU | Specific QPU hardware models | Targeted QPU hardware runs |
CPU | CPU workers on the network | Lightweight testing on the network |
LOCAL | Local binary (offline) | Unit tests, CI/CD, offline development |
GPU — Dynex Neuromorphic Chips
This is the primary compute backend. Dynex operates thousands of neuromorphic GPU chips distributed globally. When you submit a job with
ComputeBackend.GPU, it runs directly on this hardware.- Neuromorphic parallelism — thousands of chips work on your problem simultaneously
- No qubit limits — problems of arbitrary size are supported
- Always available — distributed, no single point of failure
- Linear scaling — tested up to 64 × 10⁶ variables with linear resource growth
DYNEX_SDK_KEY and DYNEX_GRPC_ENDPOINT environment variables, or from a .env file.
Full production example
QPU — Quantum Processing Unit
For specialized QPU hardware models built on top of the Dynex GPU infrastructure. Requires specifying a QPU model.Available QPU models
| Model | Constant | Description |
|---|---|---|
apollo_rc1 | QPUModel.APOLLO_RC1 | Apollo RC1 |
apollo_10000 | QPUModel.APOLLO_10000 | Apollo 10000 — large-scale |
QPU hardware has tighter constraints than GPU. Use
num_reads in the range 1–100, annealing_time in 10–1000, and shots up to 5.Coefficient bounds: qpu_max_coeff
The Apollo QPU hardware requires BQM coefficients (linear and quadratic) to stay within a bounded range. The sampler automatically checks and scales your model if needed:
qpu_max_coeff, the entire BQM is scaled down proportionally so the maximum absolute coefficient equals the threshold. The scaling is transparent — solutions are returned in the original variable space.
| Scenario | Behaviour |
|---|---|
All coefficients ≤ qpu_max_coeff | No scaling, BQM used as-is |
Any coefficient > qpu_max_coeff | BQM auto-scaled, scaling factor logged |
| Circuit BQM (QASM) | Scaling handled by Apollo API, parameter ignored |
QPU sampling example
CPU
CPU workers on the Dynex network. Useful for testing network connectivity and lightweight jobs before moving to GPU.LOCAL
Runs thedynexcore binary locally without any network connection. No SDK key required. Intended for offline development and CI/CD pipelines.
dynexcore binary in a testnet/ directory. Download from GitHub releases.
LOCAL mode is for development only. Performance does not reflect the Dynex GPU network.
Configuration via environment variables
DynexConfig parameters can be set via DYNEX_* environment variables. Constructor arguments always take priority.