Skip to content

Benchmark lower-copy Redis protocol alternatives for large payloads #37

Description

@lan17

Priority

P3 — Low — later or demand-driven enhancement.

Problem

Reads perform GET followed by string.sub in Lua, and writes concatenate the entire frame before SET. Preliminary measurements show overhead grows sharply with payload size.

Evidence:

Acceptance criteria

  • Reproduce tracked and untracked reads/writes at 100 B, 10 KB, 100 KB, and 1 MB against raw Redis operations.
  • Test the Redis 6.2 support floor and current supported Valkey.
  • Evaluate lower-copy alternatives while preserving binary serializers, ordering, targeted invalidation, and cluster routing.
  • Record Redis CPU, throughput, latency, wire round trips, and temporary memory.
  • Produce an approved design decision before changing the wire protocol.
  • Keep immediate payload guardrails in their separate issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions