PYS/IPSExtractor
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: Update testing documentation and introduce comprehensive report for IPSExtractor campaign. Add sections for executive summary, objectives, environment details, and methodology. Enhance README with compilation instructions and data sources for metrics analysis.

Browse Source
This commit is contained in:
erik
2026-07-13 21:10:43 -05:00
parent 6bf413c4ce
commit 311a4bd6d3
39 changed files with 1641 additions and 67 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/plan_pruebas/scripts/estimate_capacity.md
+25
View File
@@ -0,0 +1,25 @@
# Modelo de capacidad — 100.000 facturas/mes
No sustituye una corrida real de 100k PDFs. Usa supuestos conservadores + evidencia k6 del 2026-07-13.
## Objetivo
| Escenario | Facturas/hora necesarias |
|-----------|--------------------------|
| 100k/mes 24×7 | ≈ 139/h |
| 100k/mes jornada 8h×22d | ≈ 570/h |
## Estimaciones por etapa (host compartido 8 GiB)
| Etapa | facturas/h estimadas | vs 139/h | vs 570/h |
|-------|----------------------|----------|----------|
| Gateway (orquestación) | >>10 000 (health ~57 rps) | OK | OK |
| count-api OCR | 20–80 (CPU/RAM contención) | RIESGO | NO |
| extraction LLM | 60–200 (si cuota LLM; 30–60s/PDF, pocos workers) | ÁMBAR | NO |
| bot Selenium (1 agent) | 30–120 | RIESGO | NO |
| cleaning CSV | 500–2000 | OK | ÁMBAR |
| Pipeline completo (este host) | <50 | NO | NO |
## Escenario dedicado (condicional)
Con host ≥16–32 GiB solo IPS, OCR pool, 2+ workers extraction, cuota LLM, N agents bot: pipeline completo puede acercarse a 139–570/h según dimensionamiento.