Update Readme.md

This commit is contained in:
Natxo
2026-04-03 18:37:35 +02:00
committed by GitHub
parent 022d75e262
commit 17f2d9866c

View File

@@ -8,6 +8,31 @@
-----
## ⚡ Real-World Benchmarks
SigPro isn't just "fast on paper." In the industry-standard **JS Framework Benchmark**, it consistently outperforms the most popular libraries by operating at near-native speeds with almost zero memory overhead.
### 🚀 Execution Speed (CPU)
*Lower is better. Measured in milliseconds (ms).*
| Benchmark Test | **SigPro** | SolidJS | Vue 3 | React 18 |
| :--- | :--- | :--- | :--- | :--- |
| **Surgical Update** (10th row) | **46.8ms** | ~48ms | ~75ms | ~158ms |
| **Direct Selection** (on click) | **17.5ms** | ~18ms | ~32ms | ~65ms |
| **Initial Render** (1k rows) | **~35ms** | ~32ms | ~45ms | ~70ms |
### 🧠 Memory Footprint
*Lower is better. Measured in Megabytes (MB) after 1k rows.*
| Metric | **SigPro** | Vanilla JS | Svelte | React |
| :--- | :--- | :--- | :--- | :--- |
| **Ready Memory** (Idle) | **1.05 MB** | 1.01 MB | ~2.8 MB | ~10.4 MB |
| **Run Memory** (1k rows) | **4.90 MB** | 4.25 MB | ~10.2 MB | ~28.5 MB |
> **The Verdict:** SigPro delivers **Vanilla-like memory consumption** while maintaining **Surgical reactivity** that rivals (and often beats) SolidJS in granular updates.
---
## Why SigPro?
While other frameworks "guess" what changed by comparing massive DOM trees (Diffing), **SigPro already knows.**