Expected performance baselines for Ever Gauzy deployments.
API Benchmarksโ
Tests run with k6 against a PostgreSQL-backed instance with 4GB RAM, 2 CPUs.
Response Times (P95)โ
| Endpoint | P95 Latency | Throughput |
|---|
GET /api/health | < 10ms | 5000 req/s |
GET /api/employee | < 100ms | 500 req/s |
GET /api/task | < 150ms | 400 req/s |
GET /api/time-log | < 200ms | 300 req/s |
POST /api/task | < 200ms | 200 req/s |
POST /api/time-log | < 250ms | 200 req/s |
GET /api/report/* | < 500ms | 50 req/s |
Database Queriesโ
| Query Type | P95 Time |
|---|
| Simple SELECT | < 5ms |
| JOIN (2 tables) | < 20ms |
| JOIN (3+ tables) | < 50ms |
| Aggregate (COUNT, SUM) | < 100ms |
| Full-text search | < 200ms |
Resource Requirementsโ
Minimumโ
| Resource | Value | Supports |
|---|
| CPU | 1 core | < 10 users |
| RAM | 2 GB | Small data |
| Disk | 10 GB | Basic usage |
Recommendedโ
| Resource | Value | Supports |
|---|
| CPU | 4 cores | 50-100 users |
| RAM | 8 GB | Medium data |
| Disk | 100 GB | Full features |
Enterpriseโ
| Resource | Value | Supports |
|---|
| CPU | 8+ cores | 500+ users |
| RAM | 16+ GB | Large data |
| Disk | 500+ GB | Full history |
Optimization Tipsโ
- Enable Redis caching
- Use PostgreSQL connection pooling
- Enable query result caching
- Use CDN for static assets
- Scale horizontally for high concurrency
Related Pagesโ