Inferlab Integration for SGLang
Framework-specific planning and rendering for running SGLang servers through Inferlab. The consuming workspace supplies SGLang and its hardware runtime; this package supplies only the Inferlab integration boundary.
See the Inferlab repository for workspace authoring and supported topology documentation.
When profiling intent is enabled, the integration declares every single,
prefill, and decode model-serving replica as a capture target of the
effective mechanism. Managed collection opens the Nsight Systems range
through POST /start_profile with SGLang's CUDA_PROFILER activity and
closes it through POST /stop_profile; engine trace renders the
control-plane-assigned trace directory into SGLANG_TORCH_PROFILER_DIR and
controls the window through the same action pair with the GPU activity.
InferLab, not this package, owns the profiler lifecycle, capture plan, report
verification, cleanup, and records.
For direct single, setting enable_metrics = true enables SGLang's native
Prometheus endpoint and declares /metrics to InferLab. Without that effective
setting the integration advertises no server-metrics capability.
Metadata
Release files for inferlab-integration-sglang 0.13.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| inferlab_integration_sglang-0.13.0-py3-none-any.whl | Python 3 | none | any | Details for inferlab_integration_sglang-0.13.0-py3-none-any.whl |
Release files / inferlab_integration_sglang-0.13.0-py3-none-any.whl
| Download URL | inferlab_integration_sglang-0.13.0-py3-none-any.whl |
|---|---|
| Size | 17.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
00a6eb2f69979188b3f0e1713a22e449c787133ad43243e28b02c14997858fa6
|
|
BLAKE2b-256 checksum How to use checksums |
ce421fea0fa5e6ee0a09e6b64bb8bbc4fadc4b2368890684791f5669df6a12b3
|
| 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-sglang 0.13.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.