Engula Bench - Baseline Performance Comparison Report
Document Version: v2.1
Last Updated: 2025-09-19
Maintained by: Engula Team
Design Goals and Comparison Methodology
Goals
Compare the Get/Set throughput and latency performance of Engula 2.1 versus Redis 7.2 across different value sizes and CPU core configurations.
Metrics
- QPS (Throughput): Queries per second
- P50 (Average Latency): Median response time
Comparison Methodology
- Single-instance comparison with persistence disabled, focusing on in-memory path and protocol processing performance
- I/O thread dimension: io-threads ∈ {1, 2, 4}
- Fixed data scale, request distribution, and concurrency model for reproducible results
- Multiple value size coverage: 8B, 32B, 128B, 512B, 1KB, 2KB
Test Environment
Hardware and System
- Instances: Alibaba Cloud ECS
- ecs.c9i.xlarge / ecs.c7a.4xlarge / ecs.g8y.2xlarge
- CPU: 8 vCPU ~ 16 vCPU
- Memory: 32GB
- Operating System: CentOS 7.9
Engula Bench
This test uses the Engula Bench tool. For detailed information about the tool, please refer to the documentation: Engula Bench - Baseline Performance Comparison Tool.
Test Results
Test Environment: ecs.c9i.2xlarge
- CPU: Intel® Xeon® Granite Rapids × 8
- Memory: 16GB
- Operating System: CentOS 7.9

Test Environment: ecs.c7a.4xlarge
- CPU: AMD EPYC™ MILAN × 16
- Memory: 32GB
- Operating System: CentOS 7.9

Test Environment: ecs.g8y.2xlarge
- CPU: Yitian 710 × 8
- Memory: 32GB
- Operating System: CentOS 7.9

Summary
The benchmark results demonstrate Engula's performance characteristics across different hardware configurations and value sizes. Engula maintains competitive performance with Redis while providing significant memory savings and enhanced features.