10 Million Rows Profiled in 107 Seconds
11 analysis types. 93,604 rows/sec at steady state. 100% mathematically accurate β no sampling. Browser-only. File contents never uploaded.
Results measured on Chrome 131, Windows 11, Intel i5-12600KF, 16GB RAM. Your hardware may differ.
Verified Performance Results
Chrome 131 Β· Windows 11 Β· Intel i5-12600KF (3.70GHz) Β· 64GB RAM Β· NVMe SSD
Performance Charts
Processing time and throughput across tested dataset sizes.
Processing Time vs Dataset Size
Seconds to complete full 11-type analysis
Throughput vs Dataset Size
Rows processed per second (K/s)
Performance Variability Factors
Benchmarks were run on a controlled configuration. Real-world performance varies based on these factors:
Columns with many unique string values (e.g., free-text notes, UUID fields) require more memory for frequency counting and top-value tracking. A 10M-row file with 5 high-cardinality text columns may take 140β150 seconds instead of 107.
All 11 analysis types run per column. A 100-column file requires roughly 10Γ the correlation matrix computation vs a 10-column file. The benchmark dataset had 11 columns β files with 50+ columns will be proportionally slower.
Text parsing and pattern matching (for type detection on string values) is slower than numeric operations. Files with mostly text columns β names, addresses, descriptions β will be on the slower end of the performance range.
The benchmark used 16GB RAM with Chrome as the primary process. On machines with 8GB RAM and other applications running, large files may trigger garbage collection, significantly slowing throughput. Recommended: 16GB+ RAM for files over 5M rows.
CSV files where fields contain commas or newlines (requiring quote-wrapping) are slower to parse because each character must be checked against the quoting state machine. Simple comma-delimited files without quotes are fastest.
All 11 Analysis Types
Every type included in the benchmark. All run in a single profiling pass.
Mathematical Accuracy Verification
We verified statistical accuracy against known mathematical results before publishing benchmark claims. The 10M-row test used sequential integers 1 through 10,000,000.
Why Client-Side Processing Doesn't Compromise Speed
The profiler runs in a Web Worker β a background thread separate from the browser's UI thread. This means the page stays responsive while profiling runs. The Web Worker has direct access to the File API, reading data from disk without network round-trips.
The bottleneck is CPU and RAM, not network. On the benchmark hardware (i5-12600KF), the profiler saturates a single core for the streaming parse + analysis phase. Multi-core parallelization is possible for future versions β the single-threaded benchmark numbers are the conservative baseline.
No signup. No upload. Files never leave your browser.
Benchmarks last updated: February 2026 Β· Chrome 131 Β· Windows 11 Β· Intel i5-12600KF Β· 16GB RAM Β· Data Profiler v1.0 Β· SBPP-2026 Protocol