service-ple
Experimental, early stage. The server and the agent of service-ple as ready-built Linux commands (C++, x86-64, glibc ≥ 2.24): they keep the PLE / n-gram embedding table of Qwen3.8 / Swift Flash-Next (51 GB) out of the inference engines.
service-ple-agent: one per machine, a cache shared by every engine on it; the rows it does not have come from the local table file (XFS on NVMe; not ZFS), a central server, or both.service-ple-server: the table in RAM, served over TCP to many machines (no GPU needed).service-ple-install: installs either one as a systemd service (idempotent;-nis a dry run).service-ple-lecturas: random 4 KB reads per second of a file system (is it fast enough for the agent?).
uv tool install service-ple # or: pipx install service-ple
sudo "$(command -v service-ple-install)" agent --table /xfs/ple-fp8.safetensors # local file
sudo "$(command -v service-ple-install)" agent --server HOST:18460 --table /xfs/ple-fp8.safetensors # central server, file as fallback
sudo "$(command -v service-ple-install)" server --table /path/ple-fp8.safetensors --allow "ENGINE_HOST_1 ENGINE_HOST_2"
The vLLM side is the vllm-service-ple package (pip install vllm-service-ple in the vLLM 0.31 environment). Design, measurements and
source: https://github.com/jramirez-uab/service-ple
1 maintainer
Metadata
1 maintainer
Release files for service-ple 0.2.2
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 | Reset |
|---|---|---|---|---|
| service_ple-0.2.2-py3-none-manylinux_2_24_x86_64.manylinux_2_28_x86_64.whl | Python 3 | none | Linux glibc 2.28+ x86-64, Linux glibc 2.24+ x86-64 | Details |
Release files / service_ple-0.2.2-py3-none-manylinux_2_24_x86_64.manylinux_2_28_x86_64.whl
| Download URL | service_ple-0.2.2-py3-none-manylinux_2_24_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 161.8 kB |
| Tags | Linux glibc 2.24+ x86-64 Linux glibc 2.28+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
7770fe01cf8b53cde88fb42115b649199b8f4698cf0d0e1ce14ac35e6241c323
|
|
BLAKE2b-256 checksum How to use checksums |
91344e083cc9c51c9366252daf43cdd2ed2f307482432c80203ef0d3c350c7a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency log
