Measure published document helper small-corpus indexing throughput

This commit is contained in:
karl committed 2026-10-13 15:52:56 +02:00
1 parent 6911e97c31
commit a8249160ec
1 file changed
+13
+13
View File
@@ -202,3 +202,16 @@ benchmark and decoder tests were ignored. The previously intermittent parent
fixture passed in this serial run without changing product deadlines. This
does not replace separately executed genuine Google package checks or close
platform/GPU/visual gates.
## Small-document throughput observation
The published Linux CLI/helper indexed 100 synthetic documents on Ubuntu WSL
(50 identical one-page PDFs, 50 identical one-paragraph DOCX files, 47950 total
input bytes). CPU only, no semantic inference. Initial index: 0.893 seconds,
100 indexed, zero extraction failures. Unchanged byte-verifying rescan: 0.0124
seconds, 100 unchanged, zero failures. Both timings include CLI startup and
SQLite work; they do not isolate parser startup or represent large real documents,
Windows throughput, cold filesystem caches or steady-state search latency.
No persistent parser/cache optimization is justified by this small observation.
Raw ignored report: `.searchi/qa/document-throughput-013.json`, SHA-256
`b86df0bf2ca0953317033b35b4642e6e0fadb93e50c499a7a28b1ae82512acd1`.