Published scale evidence: a load test with a stated method

Abierto
  • ¿Algo no está bien?
#1,608 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
15/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
aws, docker-compose, postgresql
Área
documentation, performance

Línea de trabajo

Start from the four hot paths named in the issue: GET /api/v1/feature-flags/evaluate/{key}, POST /api/v1/tracking/assign, POST /api/v1/tracking/track and /batch, and the SDK ruleset. Read the Compose stack and, if reachable, the CDK stack to record the deployment shape, then choose a load generator and a method. Done means a committed script, a measured run with RPS, p50/p95/p99 and error rate, and a docs page stating setup and limits. Any billed cloud run needs the founder's approval first.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement

Events are stored in PostgreSQL, and no throughput figures are published. A team evaluating a self-hosted platform asks "will it hold my traffic?" before anything else, and today there is no answer to point to.

Wanted before launch (founder, 2026-11-02): published scale evidence, a load test with a stated method.

  • The hot paths an integrating app drives: flag evaluation (GET /api/v1/feature-flags/evaluate/{key}), assignment (POST /api/v1/tracking/assign), event tracking (POST /api/v1/tracking/track and /batch), and the SDK ruleset.
  • A stated setup: the deployment shape (the Compose stack, and if possible the CDK stack), instance sizes, data volume already in the database, concurrency, duration, and where the load generator runs.
  • Results as requests per second and latency percentiles (p50, p95, p99) and the error rate, with the point where it stops keeping up and what saturates first.
  • The script and the method committed, so anyone can repeat it; a docs page that states the numbers, the setup and what was not measured.
  • Numbers come from a measured run, never estimated; a single wall-clock timing is not a gate.

Where it runs (a laptop, a CI runner, or a billed cloud environment) is decided in the plan; anything that bills waits for the founder at that moment.

Lenguaje dominante
Python
Estrellas
0
Forks
4
Merge medio
5 h 36 min
PR fusionados (30 d)
509

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Controlvar/controlvar

Todos los issues de Controlvar/controlvar

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.