Benchmarks

This page summarizes curated benchmark results for Eden's Eve gateway runtime.

Raw benchmark artifacts are environment-specific and are intentionally not

committed. Treat these numbers as a public performance brief from controlled

internal runs, not as a universal hardware guarantee.

Redis is the only production-ready gateway protocol in this release. Results for

AI/LLM, agent, Postgres, Mongo, and other protocol surfaces should be read as

development and evaluation data until those surfaces are explicitly promoted.

Summary

Eve is Eden's high-performance data plane. It proxies Redis traffic and

OpenAI-compatible AI workloads while preserving layer-7 awareness for policy,

analysis, routing, mirroring, migration, and telemetry.

The key result from the current benchmark set: Eve is competitive with Envoy on

raw gateway throughput while doing substantially more product work inline. On a

matched Redis workload, Eve used about one-third less CPU per completed request

than Envoy and produced lower tail latency.

Redis Gateway

Matched Throughput

At a controlled 400k req/s mixed Redis load where both gateways completed the

same work without shedding, Eve matched Envoy throughput with lower latency and

lower CPU use.

CPU attribution from the sampled run:

Direct Redis was saturated at this offered load, so it is best read as a

saturation signal rather than an added-latency baseline.

Overload Behavior

In a 400k offered open-loop Redis load, Eve sustained materially more completed

throughput than Envoy while avoiding shed.

With telemetry export and capture-all request analysis enabled, Eve still held

384k req/s at zero shed with p99 3.93 ms on this workload.

Large Payload Throughput

On 64 KiB Redis GET workloads, Eve was competitive with Envoy on wire

throughput and showed cleaner error behavior at saturation.

The ceiling in these runs was the backend, host, and TCP path rather than only

gateway worker count.

AI And LLM Gateway

Eve exposes an OpenAI-compatible AI gateway for chat, multi-agent/tool, and

streaming workloads. These runs used a synthetic OpenAI-compatible backend and a

generic Envoy HTTP proxy.

Sustained Load

Latency

For small-response LLM traffic, recent fast-path work allowed Eve to hold a full

12k req/s at about 1.2 ms p99 with zero shedding.

Observability Validation

Eve telemetry was validated end-to-end under live Redis load. In a 30-minute

window with a 100k-request Redis workload running at 175,472 req/s, the runtime

produced:

• 185 metrics across core, gateway, LLM, IAM, endpoint, workload, migration,

tool-safety, and analytics groups.

• 14,043 gateway metric rows stored in ClickHouse, including request and command

counts, per-command duration, endpoint-vs-overhead timing, parse

decode/materialize breakdown, bridge queue/write timing, byte counters, and

mirror latency/divergence.

• 2,105 trace spans captured and queryable alongside structured logs.
• Dashboard series coverage from emission through storage, query, and UI.

This matters because Eve's performance profile includes built-in protocol-aware

observability rather than only generic proxy counters.

Capability Context

The raw numbers should be read alongside the feature set being exercised. Redis

is one measured protocol in this report, but the product surface is broader:

Eden is a data and AI gateway for databases, model providers, and agent

workloads.

Reproducing Workloads

Source benchmark tools live in the repository's

benchmark/

directory:

• cacophony runs open-loop Redis workloads against a Redis-compatible target.
• ai-workload runs synthetic OpenAI-compatible HTTP workloads.

Keep raw result files, profiler captures, and host-specific scenario files

outside the repository unless they are deliberately curated for publication.