Skip to main content

PegaFlow Python Package

High-performance key-value storage engine with Python bindings, built with Rust and PyO3.

Features

  • PegaEngine: Fast Rust-based key-value storage with Python bindings
  • PegaKVConnector: vLLM KV connector for distributed inference with KV cache transfer

Installation

From Source

# Install maturin if you haven't already
pip install maturin

# Build and install in development mode
cd python
maturin develop

# Or build a wheel
maturin build --release

From PyPI (coming soon)

pip install pegaflow

Usage

Basic KV Storage

from pegaflow import PegaEngine

# Create a new engine
engine = PegaEngine()

# Store key-value pairs
engine.put("name", "PegaFlow")
engine.put("version", "0.1.0")

# Retrieve values
name = engine.get("name")  # Returns "PegaFlow"
missing = engine.get("nonexistent")  # Returns None

# Remove keys
removed = engine.remove("name")  # Returns "PegaFlow"

vLLM KV Connector

from vllm import LLM
from vllm.distributed.kv_transfer.kv_transfer_agent import KVTransferConfig

# Configure vLLM to use PegaKVConnector
kv_transfer_config = KVTransferConfig(
    kv_connector="PegaKVConnector",
    kv_role="kv_both",
    kv_connector_module_path="pegaflow.connector",
)

# Create LLM with KV transfer enabled
llm = LLM(
    model="gpt2",
    kv_transfer_config=kv_transfer_config,
)

Connector Modes

PegaKVConnector defaults to read_write: it queries PegaFlow for reusable KV blocks, loads matched blocks into vLLM, and saves newly computed full blocks back to PegaFlow.

Set pegaflow.mode to save_only when another vLLM connector is responsible for reads and PegaFlow should only persist KV blocks for later reuse. This is intended for MultiConnector decode-side setups where an upstream connector owns the external hit/load path, while PegaFlow records the resulting KV cache. In save_only mode, PegaFlow does not query or load KV blocks.

vllm serve Qwen/Qwen3-0.6B \
  --kv-transfer-config '{
    "kv_connector": "MultiConnector",
    "kv_role": "kv_both",
    "kv_connector_extra_config": {
      "connectors": [
        {
          "kv_connector": "<external-read-connector>",
          "kv_role": "kv_both"
        },
        {
          "kv_connector": "PegaKVConnector",
          "kv_role": "kv_both",
          "kv_connector_module_path": "pegaflow.connector",
          "kv_connector_extra_config": {
            "pegaflow.mode": "save_only"
          }
        }
      ]
    }
  }'

Valid values are read_write and save_only.

TP Shards Across Hosts

CUDA IPC is host-local. When one tensor-parallel replica spans multiple hosts, run one PegaFlow server on each host and configure the connector with every server endpoint in global TP-rank order:

{
  "kv_connector": "PegaKVConnector",
  "kv_role": "kv_both",
  "kv_connector_module_path": "pegaflow.connector",
  "kv_connector_extra_config": {
    "pegaflow.tp_shard_endpoints": [
      "http://host-a:50055",
      "http://host-b:50055"
    ]
  }
}

For TP8 and two endpoints, global ranks 0-3 register with the first server and ranks 4-7 register with the second. Each server sees a local TP4 topology and must manage the four GPUs on its own host. Every vLLM process must receive the same ordered endpoint list.

The scheduler queries every shard and only reuses the prefix available from all of them. Each worker loads with the lease issued by its local server. The connector gives every shard a distinct namespace, so deployments with a different host split cannot reuse an incompatible cache layout.

TP sharding currently requires equal contiguous shards and TP-only parallelism. Pipeline, decode-context, and prefill-context parallelism are rejected when more than one endpoint is configured.

P/D Partial Tail Blocks

vLLM normally exposes hashes only for complete KV blocks. In a P/D deployment, enable pegaflow.pd_tail_save on prefill and pegaflow.pd_tail_load on decode to reuse the final partial prompt block as well. Start both vLLM processes with the same explicit PYTHONHASHSEED and --prefix-caching-hash-algo xxhash_cbor.

Prefill: {"pegaflow.pd_tail_save": true}

Decode: {"pegaflow.pd_tail_load": true, "pegaflow.wait_for_full_prefix": true}

pegaflow.wait_for_full_prefix makes decode wait (up to 30s) until the full prompt prefix is fetchable from a remote node via MetaServer + RDMA. It only applies when prefill and decode run separate engines; it does not observe saves landing in a shared/local engine and has no effect when RDMA is not configured.

Development

See the examples directory for more usage examples.

Testing

Running Unit Tests

The test suite includes integration tests that verify the EngineRpcClient can correctly communicate with a running pegaflow-server instance.

Prerequisites

  1. Build the Rust extension:

    cd python
    maturin develop --release
    
  2. Build the server binary:

    cd ..
    cargo build --release --bin pegaflow-server
    
  3. Ensure CUDA is available (tests require GPU):

    python -c "import torch; assert torch.cuda.is_available()"
    

Running Tests

cd python

# Run all tests
pytest tests/ -v

# Run specific test file
pytest tests/test_engine_client.py -v

# Run with coverage
pytest tests/ --cov=pegaflow --cov-report=html

Test Structure

  • tests/conftest.py: Contains pytest fixtures for:

    • pega_server: Automatically starts/stops pegaflow-server for integration tests
    • engine_client: Creates an EngineRpcClient connected to the test server
    • client_context: Provides a ClientContext representing a vLLM instance with GPU KV cache tensors
    • registered_instance: Provides a registered instance ID for query tests
  • tests/test_engine_client.py: Integration tests for:

    • Server connectivity
    • Query operations with various inputs

Test Fixtures

The ClientContext class abstracts a vLLM instance and provides:

  • register_kv_caches(): Register GPU KV cache tensors with the server
  • query(block_hashes): Query available blocks
  • unregister_context(): Unregister context from server

Example test usage:

def test_query(client_context):
    """Test query operation."""
    result = client_context.query([])
    assert result is not None

License

MIT

Metadata

Release files for pegaflow-llm-cu13 0.24.5

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

Built distributions (wheels)

Table of built distributions (wheels) for pegaflow-llm-cu13 0.24.5
File
pegaflow_llm_cu13-0.24.5-cp314-cp314-manylinux_2_34_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.34+ x86-64 Details
pegaflow_llm_cu13-0.24.5-cp314-cp314-manylinux_2_34_aarch64.whl CPython 3.14 CPython 3.14 Linux glibc 2.34+ ARM64 Details
pegaflow_llm_cu13-0.24.5-cp313-cp313-manylinux_2_34_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.34+ x86-64 Details
pegaflow_llm_cu13-0.24.5-cp313-cp313-manylinux_2_34_aarch64.whl CPython 3.13 CPython 3.13 Linux glibc 2.34+ ARM64 Details
pegaflow_llm_cu13-0.24.5-cp312-cp312-manylinux_2_34_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.34+ x86-64 Details
pegaflow_llm_cu13-0.24.5-cp312-cp312-manylinux_2_34_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.34+ ARM64 Details
pegaflow_llm_cu13-0.24.5-cp311-cp311-manylinux_2_34_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.34+ x86-64 Details
pegaflow_llm_cu13-0.24.5-cp311-cp311-manylinux_2_34_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.34+ ARM64 Details
pegaflow_llm_cu13-0.24.5-cp310-cp310-manylinux_2_34_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.34+ x86-64 Details
pegaflow_llm_cu13-0.24.5-cp310-cp310-manylinux_2_34_aarch64.whl CPython 3.10 CPython 3.10 Linux glibc 2.34+ ARM64 Details

Total release size: 79.7 MB

Release files / pegaflow_llm_cu13-0.24.5-cp314-cp314-manylinux_2_34_x86_64.whl

Download URL pegaflow_llm_cu13-0.24.5-cp314-cp314-manylinux_2_34_x86_64.whl
Size 8.0 MB
Tags CPython 3.14 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
cf1b3b86deb2e69d763eb1e9c6841a0e0e6b04d3f3a58846394a91a396ac6a71
BLAKE2b-256 checksum
How to use checksums
a221d69aea1ab05af5ad3a77ed52fc3cd703b90ed6f5661619c56409e3a4f7aa
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.14

Release files / pegaflow_llm_cu13-0.24.5-cp314-cp314-manylinux_2_34_aarch64.whl

Download URL pegaflow_llm_cu13-0.24.5-cp314-cp314-manylinux_2_34_aarch64.whl
Size 7.9 MB
Tags CPython 3.14 Linux glibc 2.34+ ARM64
SHA-256 checksum
How to use checksums
485e9cf996160662e38f8725ec3088506a8126b033efb5e43325b13298bc5500
BLAKE2b-256 checksum
How to use checksums
9816a68b7321d53ec60102164a970232ee868457c2b869d815a51ffa25f8d671
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.14

Release files / pegaflow_llm_cu13-0.24.5-cp313-cp313-manylinux_2_34_x86_64.whl

Download URL pegaflow_llm_cu13-0.24.5-cp313-cp313-manylinux_2_34_x86_64.whl
Size 8.0 MB
Tags CPython 3.13 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
65f1887789a94933369cf38df42dd4cf38bf07b828766c5c3e3b86094aee180c
BLAKE2b-256 checksum
How to use checksums
dbfd98f6013c79292f268f0e066f4a68b3a846f0f54abb47fcdd045160d4230f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.14

Release files / pegaflow_llm_cu13-0.24.5-cp313-cp313-manylinux_2_34_aarch64.whl

Download URL pegaflow_llm_cu13-0.24.5-cp313-cp313-manylinux_2_34_aarch64.whl
Size 7.9 MB
Tags CPython 3.13 Linux glibc 2.34+ ARM64
SHA-256 checksum
How to use checksums
cbf0c79c7a5983b7d3eb6f1a68d632f2681457f69a8771debf999f35a3b4ac9f
BLAKE2b-256 checksum
How to use checksums
3ae23c9479f9209f7a45f21bbbdf163015913fcf2b5e3bdf95e8ecd564f4dc95
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.14

Release files / pegaflow_llm_cu13-0.24.5-cp312-cp312-manylinux_2_34_x86_64.whl

Download URL pegaflow_llm_cu13-0.24.5-cp312-cp312-manylinux_2_34_x86_64.whl
Size 8.0 MB
Tags CPython 3.12 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
cf85aad51c562f394f51e7ebf68b608cdf7a7230c4130f5e0fca7e06ab5724cf
BLAKE2b-256 checksum
How to use checksums
dbac88b6766d05518303245dbe2d4ce171cd1df1b3aaa4636b8485baa3d3b7c0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.14

Release files / pegaflow_llm_cu13-0.24.5-cp312-cp312-manylinux_2_34_aarch64.whl

Download URL pegaflow_llm_cu13-0.24.5-cp312-cp312-manylinux_2_34_aarch64.whl
Size 7.9 MB
Tags CPython 3.12 Linux glibc 2.34+ ARM64
SHA-256 checksum
How to use checksums
1565c7e6923c05e6d55a31711de98497cf0a6e0fabff6329caa9c4fcd80fd177
BLAKE2b-256 checksum
How to use checksums
6fea2ab37a68df38063097d810adc30dd6b1fcc6eeb21c665c6633b5222bf11d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.14

Release files / pegaflow_llm_cu13-0.24.5-cp311-cp311-manylinux_2_34_x86_64.whl

Download URL pegaflow_llm_cu13-0.24.5-cp311-cp311-manylinux_2_34_x86_64.whl
Size 8.0 MB
Tags CPython 3.11 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
e46a4699ed1877aa8dd3b295dcb8670d77f1301eb0fe771953343fafeaf707c0
BLAKE2b-256 checksum
How to use checksums
4497a0ccc763cf3051f2a70c41c13043c1a6ab844bd2fe4ac8aecbbc1f7560c9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.14

Release files / pegaflow_llm_cu13-0.24.5-cp311-cp311-manylinux_2_34_aarch64.whl

Download URL pegaflow_llm_cu13-0.24.5-cp311-cp311-manylinux_2_34_aarch64.whl
Size 7.9 MB
Tags CPython 3.11 Linux glibc 2.34+ ARM64
SHA-256 checksum
How to use checksums
505e10a3a921477c44306243dbf82ae2107253547c4f13b6b55269935d447737
BLAKE2b-256 checksum
How to use checksums
a1d818f28dad25a249008429eb0ccabe316d1f9759c29f40c1315d3fa5ec97d8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.14

Release files / pegaflow_llm_cu13-0.24.5-cp310-cp310-manylinux_2_34_x86_64.whl

Download URL pegaflow_llm_cu13-0.24.5-cp310-cp310-manylinux_2_34_x86_64.whl
Size 8.0 MB
Tags CPython 3.10 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
066f0db4026f97615373c9bffb3d00fff2b5c32d4d74537fa86a76bcf5bc6a8b
BLAKE2b-256 checksum
How to use checksums
09e7b640c949bbf75b18c3d6e086a45acb332dfe542f6353f403b7648a41a65b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.14

Release files / pegaflow_llm_cu13-0.24.5-cp310-cp310-manylinux_2_34_aarch64.whl

Download URL pegaflow_llm_cu13-0.24.5-cp310-cp310-manylinux_2_34_aarch64.whl
Size 7.9 MB
Tags CPython 3.10 Linux glibc 2.34+ ARM64
SHA-256 checksum
How to use checksums
41a594a5ccd361fe1b0d24eb700036c8264180dbfb733ffccb17925460d46869
BLAKE2b-256 checksum
How to use checksums
e66577b1dd81b7c629aa84cbbf2de779dc48191c5521fa5059e152711decebb9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.14

Security for pegaflow-llm-cu13 0.24.5

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.

Release history Release notifications | RSS feed

This release

0.24.5 This release

10 release files No provenance

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