leideng/QCFuse/srt/mem_cache/storage/nixl - Storage Bucket

NIXL Integration for HiCache

This directory contains the NIXL (NVIDIA Inference Xfer Library) integration for HiCache, enabling high-performance storage across multiple backends.

NIXL provides a unified API for accessing various storage plugins, including but not limited to:

• Deepseek's 3FS APIs for high-throughput file operations
• GPU Direct Storage (GDS) for direct data movement between storage and GPU memory, bypassing CPU memory copies
• Amazon S3-compatible object storage for key-value access patterns

Additional backend integrations are planned for future releases.

NIXL Resources

• Project Repository: NIXL on GitHub
• Documentation: NIXL Documentation

Overview

The NIXL integration consists of two main files:

• hicache_nixl.py - Main HiCache storage connector using NIXL
• nixl_utils.py - Utility classes for backend selection, registration, and file management

Components

HiCacheNixl

The main storage connector that provides:

• Single and batch tensor set/get operations
• Automatic backend selection (3FS > POSIX > GDS_MT > GDS > OBJ)
• High-performance file-based (or) object based storage access using NIXL

NixlUtils

Consolidated utility classes:

• NixlBackendSelection - Handles backend selection and creation
• NixlRegistration - Manages memory registration for tensors, files and objects
• NixlFileManager - Handles file system operations and NIXL tuple creation

Using NIXL for HiCache backend

When running the SGLang server, indicate nixl for hicache-storage-backend parameter, for instance:

python3 -m sglang.launch_server --model-path <model> --host <ip> --port <port> --page-size 64 --enable-hierarchical-cache --hicache-ratio 2 --hicache-size 64 --hicache-write-policy write_through --hicache-storage-backend nixl

To customize the base directory for files, you can set the following environment variable:

export SGLANG_HICACHE_NIXL_BACKEND_STORAGE_DIR=/path/to/desired/dir

Selection of any storage backend like 3FS requires availability of that library on the system, and the backend is selected based on the priority mentioned above.

Running Unit Tests

Prerequisites

• NIXL library installed and available (latest main required for supporting object query)
• PyTorch installed
• Python 3.8+

Unit tests from current directory

From the current directory run:

Run all NIXL tests:

PYTHONPATH=. python -m pytest test_hicache_nixl_storage.py -o asyncio_mode=strict

Run with verbose output:

PYTHONPATH=. python -m pytest test_hicache_nixl_storage.py -v -o asyncio_mode=strict

Note: The -v flag provides more detailed output, showing each test case name and its result.

Run a specific test:

PYTHONPATH=. python -m pytest test_hicache_nixl_storage.py -v -k test_single_set_get -o asyncio_mode=strict

Note: The -o asyncio_mode=strict flag is added to suppress warnings about asyncio configuration. This is not required for test functionality but provides cleaner output.

Test Coverage

Tests for this integration, a test suite can be found at test_hicache_nixl_storage.py which covers:

HiCache Integration Tests (4 tests)

• Single tensor set/get operations
• Batch tensor set/get operations
• Mixed single and batch operations
• Data integrity for various tensor types

File Management Tests (5 tests)

• Basic file operations
• NIXL tuple creation
• Error handling in file operations

Registration Tests (2 tests)

• Tensor registration with memory type detection
• File registration using NIXL tuples

Expected Output

When tests run successfully, you should see:

• NIXL agent initialization messages
• Backend selection messages (e.g., "Backend POSIX was instantiated")
• Test results with "ok" for passed tests
• Summary showing "Ran X tests in Y seconds" and "OK"

Troubleshooting

Import Errors

If you encounter ModuleNotFoundError, ensure:

• You're running from the correct directory
• PYTHONPATH is set correctly
• NIXL library is properly installed

NIXL Errors

If NIXL operations fail:

• Check that NIXL is properly installed
• Verify that required plugins are available
• Ensure file permissions are correct for test directories

File Structure

python/sglang/srt/mem_cache/nixl/
├── hicache_nixl.py          # Main HiCache storage connector
├── nixl_utils.py            # All NIXL utility classes
├── README.md                # This file
└── tests/
    └── test_nixl_unified.py # All tests in one file

Dependencies

• NIXL: NVIDIA Inference Xfer Library (version 0.4 or later)
  • Required plugins: POSIX (minimum), 3FS/GDS (optional for better performance)
  • See NIXL Installation Guide
• PyTorch: For tensor operations (version 1.8 or later)
• Python 3.8+: For type hints and modern features

Supported Features

Memory Types

• Tensor side: multi-dimensional tensors of all numeric types (int32, int64, float32, float64) are supported.

  • Tensors can be on CPU or GPU (as long as a GPU capable backend such as GDS_MT is available).
  • Currently each tensor is mapped to a file or key, but it can be extended to support multiple keys per file or key.

• Storage side: file and object are supported through their relevant backends (e.g., 3FS or OBJ).

Backend Priority

The NIXL backend selection follows this priority order:

1. 3FS - Highest performance (if available)
   • Best for high-throughput file operations using Deepseek 3FS APIs
2. POSIX - Standard file I/O (fallback)
   • Universal compatibility
   • Good for development and testing - Leverages both libaio/liburing
3. GDS_MT - Multi-threaded GDS (if available)
   • Optimized for concurrent operations
   • Supports GPU Direct storage with multiple light weight threads
4. GDS - GPU Direct Storage (if available)
   • Direct GPU-storage data path
   • Best for filesystems benefiting from batch operations and smaller IOs.
5. OBJ - Amazon S3 based Object Storage
   • Key-value based storage The system automatically selects the best available backend, with POSIX as the default fallback.

Note

This is v0 of the NIXL connector. Future versions will focus on further performance optimizations such as memory pre-registration (pre-allocating and registering memory buffers to reduce registration overhead during transfers) and block merging (combining related blocks as offsets within the same file to reduce file operations and improve throughput). These optimizations require changes at a higher layer, as the current HiCache API doesn't expose information like block relationships or hash patterns that would enable these optimizations.