Skip to main content

Inferlab Integration for Specialized Engines

This package connects Inferlab to a hardware-by-model Specialized Engine that implements the canonical inferlab-token-engine smg-worker command. The Engine accepts prompt token IDs and returns generated token IDs over SMG's worker protocol. TokenSpeed SMG remains responsible for the public HTTP API, tokenization, chat templates, detokenization, and response formatting.

The integration contains no model-, architecture-, hardware-, or Engine-implementation-specific lowering. A downstream workspace supplies the Rust Engine binary, SMG, model intent, source revision, locked environment, and private placement bindings. Consequently, a new conforming Engine does not need another Inferlab integration package.

The supported shape is deliberately closed: one single Engine replica in one process behind one SMG Gateway. The process owns an arbitrary nonzero pure-TP device set; attention, expert, and dense-expert tensor parallelism all equal the outer TP width, while pipeline, data, context, and expert parallelism stay at one. The contract remains serial and has no P/D Router, KV-transfer, batching, or Engine-local profiling surface. InferLab can profile the Engine process tree while TokenSpeed SMG exposes the capture-window POST /start_profile and POST /stop_profile actions on the Gateway.

The Gateway exposes server metrics on its separately allocated prometheus port. The integration selects SMG's single-target least_load policy so its canonical worker monitor polls Engine load fields while retaining the same sole routing target. In the current downstream validation, that endpoint exported SMG-owned metric families but no smg_engine_* families, so Engine-series re-export remains a downstream qualification gap.

Metadata

Release files for inferlab-integration-specialized-engine 0.12.0

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

Built distribution (wheel)

Table of built distributions (wheels) for inferlab-integration-specialized-engine 0.12.0
File Interpreter ABI Platform Actions
inferlab_integration_specialized_engine-0.12.0-py3-none-any.whl Python 3 none any Details for inferlab_integration_specialized_engine-0.12.0-py3-none-any.whl

Release files / inferlab_integration_specialized_engine-0.12.0-py3-none-any.whl

Download URL inferlab_integration_specialized_engine-0.12.0-py3-none-any.whl
Size 9.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
1a7445c74849daa0493c34ca40f8a0f39b650654f3d7e0894fb0841c0a7e98d5
BLAKE2b-256 checksum
How to use checksums
f034f95d361e9fa7e456a7c4e565ea265caa7f1336029a82cd5f3a1e3aca5dbe
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.6

Security for inferlab-integration-specialized-engine 0.12.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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page