mirror of
https://github.com/tiennm99/thptqg.git
synced 2026-10-04 18:13:58 +00:00
tiennm99
d7e2fa2d12
The whole design rests on a claim nobody has measured: that a lookup fetches a few hundred KB rather than the file. Every query now reports what it actually cost. [httpvfs] name "nguyen buu loc" seeking "buu" — 14 request(s), 78 KB, 212 ms · session 31 request(s), 180 KB of 302.4 MB The numbers come from the worker's getStats() rather than its bytesRead counter: bytesRead is the budget accumulator and resets itself to zero the moment a query trips the ceiling, so it would under-report exactly when the number matters. getStats() reports per-file totals including what the read heads prefetched, which is the honest figure — prefetch overfetch is invisible to a page count. Opening a database logs too, since the header and schema pages are read before any query and would otherwise inflate the first search. The SQL tab shows the same pair on screen: this query, then the session.