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

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

Download URL pegaflow_llm_cu13-0.24.2-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
79d75d810edbc055e2e9c7774f874bdaab50509fd86049b3b69643091fa3acd4
BLAKE2b-256 checksum
How to use checksums
d8492defec84f380ad7b23dd1a1163971048bd41584cfc6f6f7e2347a267f1e9
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.2-cp314-cp314-manylinux_2_34_aarch64.whl

Download URL pegaflow_llm_cu13-0.24.2-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
f6950e2c5082dbcc14a3c88aa1fce7996267b6193cf49359474f9fafbd0a2fcc
BLAKE2b-256 checksum
How to use checksums
093b63212aa348342a4e723b7c257e1aca7244b4cb82f843e7f537ee8cb11f2a
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.2-cp313-cp313-manylinux_2_34_x86_64.whl

Download URL pegaflow_llm_cu13-0.24.2-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
70bd274f8d31089e0f3191afc270db6d1e9ae60ed27956c1593495d588cc6f91
BLAKE2b-256 checksum
How to use checksums
03920bd3ab567ab86f6fa298b23509598c7d776a46b35f7e94120f3842b56aa7
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.2-cp313-cp313-manylinux_2_34_aarch64.whl

Download URL pegaflow_llm_cu13-0.24.2-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
b4bc653b7517e924a06185a66c11ddea1cb7b4d0034c590f687adf44d6dd60f2
BLAKE2b-256 checksum
How to use checksums
c16f968c39c98969394595f3aa5b673afa8fe61655c02d93bcfe142353e85d77
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.2-cp312-cp312-manylinux_2_34_x86_64.whl

Download URL pegaflow_llm_cu13-0.24.2-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
f015d4f24b09f9a1cb8337b8b7fda0dec41a56645d5fc4280d2c88d7e7516f98
BLAKE2b-256 checksum
How to use checksums
b85eceaa01eea4b85c907bded7828e570d8976e234430f9da2e16cb36a1cb25c
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.2-cp312-cp312-manylinux_2_34_aarch64.whl

Download URL pegaflow_llm_cu13-0.24.2-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
726a53b46c30d13b719e1fad5a444d44e8e830deb8992829f217db5d94a761d9
BLAKE2b-256 checksum
How to use checksums
87aeacc3ee995db628815491e9049f83d77ac97c3affc1cabe3d61d3206ac67b
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.2-cp311-cp311-manylinux_2_34_x86_64.whl

Download URL pegaflow_llm_cu13-0.24.2-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
e7393c5787d25fe76f2ed0e98e08063c19793d494abb79baf1647951017b081a
BLAKE2b-256 checksum
How to use checksums
7a8eb966ed2bc193f680fec7282f8a623c126bfbccb8f03be104c0a54700374f
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.2-cp311-cp311-manylinux_2_34_aarch64.whl

Download URL pegaflow_llm_cu13-0.24.2-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
9c2e213efc9a8605c5563cfc19cf552c93873b7650d35532747aa5431e3d8d20
BLAKE2b-256 checksum
How to use checksums
d96e680697e9fc0809b7275775b5d9ef0edd2222120a279c93571bad24fe0e84
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.2-cp310-cp310-manylinux_2_34_x86_64.whl

Download URL pegaflow_llm_cu13-0.24.2-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
4e2653365d18797bf8e4c5ec731fb204274ecde635480083faa0517d9fd378c6
BLAKE2b-256 checksum
How to use checksums
ce4c0da4d518a0901b66711a570e30470731f005748e3727b031c2a640dd5f42
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.2-cp310-cp310-manylinux_2_34_aarch64.whl

Download URL pegaflow_llm_cu13-0.24.2-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
b59975bd2aafe662e1ad94b512a019643e65151688bce95edb0cc98a03c588ba
BLAKE2b-256 checksum
How to use checksums
e00f6f6facb31a5f3e9f1bed08c9a0e522bfc275ea0cea4ee29b9b85e382fb44
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.2

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