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.3

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.3
File
pegaflow_llm_cu13-0.24.3-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.3-cp314-cp314-manylinux_2_34_aarch64.whl CPython 3.14 CPython 3.14 Linux glibc 2.34+ ARM64 Details
pegaflow_llm_cu13-0.24.3-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.3-cp313-cp313-manylinux_2_34_aarch64.whl CPython 3.13 CPython 3.13 Linux glibc 2.34+ ARM64 Details
pegaflow_llm_cu13-0.24.3-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.3-cp312-cp312-manylinux_2_34_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.34+ ARM64 Details
pegaflow_llm_cu13-0.24.3-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.3-cp311-cp311-manylinux_2_34_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.34+ ARM64 Details
pegaflow_llm_cu13-0.24.3-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.3-cp310-cp310-manylinux_2_34_aarch64.whl CPython 3.10 CPython 3.10 Linux glibc 2.34+ ARM64 Details

Total release size: 79.3 MB

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

Download URL pegaflow_llm_cu13-0.24.3-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
4a1e2d9524c21114eabc8657f33e71a86e00127628b185774484c03aabc149fe
BLAKE2b-256 checksum
How to use checksums
393d873979b9a758a8e51649bfc4d0bbefff4cbb3ab9d813c001b6b0cf65a0cd
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.3-cp314-cp314-manylinux_2_34_aarch64.whl

Download URL pegaflow_llm_cu13-0.24.3-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
d29af51697c7be4efb8df6f7bf2aafa2d8450ba1a5b03a30042eab292906ac09
BLAKE2b-256 checksum
How to use checksums
050ab419602341cc9292a4a22baf292c7b90b578f9dfbe3429e63dfa96760684
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.3-cp313-cp313-manylinux_2_34_x86_64.whl

Download URL pegaflow_llm_cu13-0.24.3-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
9db5e0102e7cccf8e3896d9ea864348efed73aa9144a042c9276a63df58e827f
BLAKE2b-256 checksum
How to use checksums
ce1bbcac08a106fae8671a983f8b07568a47ba54906f51563e2984328ffa0dea
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.3-cp313-cp313-manylinux_2_34_aarch64.whl

Download URL pegaflow_llm_cu13-0.24.3-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
e39c19a36a611601f1be5381cf81afa3582816e5d7cd8d1bcbcc3329f901e7d7
BLAKE2b-256 checksum
How to use checksums
338a81f779ef5afae9475063f7a304932c653b3094811e68a85d6a7da40ea005
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.3-cp312-cp312-manylinux_2_34_x86_64.whl

Download URL pegaflow_llm_cu13-0.24.3-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
b0e63d55ac02c7070aceb804afb6a6dd66244e1ab9e671a9fa8ec4cfaebb6a03
BLAKE2b-256 checksum
How to use checksums
89067fed58c706ff4b23ee98a7ae822545ca7940da7e3f84d272597b501674c0
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.3-cp312-cp312-manylinux_2_34_aarch64.whl

Download URL pegaflow_llm_cu13-0.24.3-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
5aba8698e8cb249479d3410157f0d5be77e63b160a9231fcd0ec4e848e3efa94
BLAKE2b-256 checksum
How to use checksums
bf4e1fbcb6260a7b00d78168609306a90d12372c88ab80ae6259c597c06b657f
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.3-cp311-cp311-manylinux_2_34_x86_64.whl

Download URL pegaflow_llm_cu13-0.24.3-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
e63c08b2558f5612753b5c0873e9a418c99652455867231c1257021b49dc1b34
BLAKE2b-256 checksum
How to use checksums
cded401a67777759764f5fda30b57b6e6b4ef1b745aaff6f22ad8270f34ffa8a
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.3-cp311-cp311-manylinux_2_34_aarch64.whl

Download URL pegaflow_llm_cu13-0.24.3-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
a87fdeb95271ad202d61e51b269c10c3575328f24c1840cbd47b449cb190feea
BLAKE2b-256 checksum
How to use checksums
6cf0ea1ba7bee9248634a11230679bdbb9f7a4c811f36b58c4899d6053f38a3d
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.3-cp310-cp310-manylinux_2_34_x86_64.whl

Download URL pegaflow_llm_cu13-0.24.3-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
f263ef313772d297420b1e6a38f4b88a0c0fa3d5606c9c4c32d9fa53c09a9730
BLAKE2b-256 checksum
How to use checksums
4f56ff060c17f3c64adc37f6c33f172d85a62a889297836c572d8c266f39f037
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.3-cp310-cp310-manylinux_2_34_aarch64.whl

Download URL pegaflow_llm_cu13-0.24.3-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
62ee1791e8cc571b5d306120bea18394304ddd2453f737801d5f0b4d0287d0a7
BLAKE2b-256 checksum
How to use checksums
1e5bd4a6a10b1515f9bd01c5b1448bae79e508f29222867cd98f78df4e67f0b1
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.3

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.3 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