rust/greptimedb
1
0
Fork 0
mirror of https://github.com/GreptimeTeam/greptimedb.git synced 2026-10-13 15:32:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(perf): clarify BSS baseline and storage measurement scope

Browse Source 
Signed-off-by: discord9 <55937128+discord9@users.noreply.github.com>
This commit is contained in:
discord9
2026-09-08 14:06:08 +08:00
parent de843771f1
commit 932be19b06
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/perf/query_cases/sst_float_bss/RESULTS.md
+5 -1
View File
@@ -29,7 +29,11 @@ The inspection covered `data/greptime/public` only. Each target had six selected
SSTs, 4,423,680 rows, and 45 inspected `greptime_value` chunks. Footer checks
found no BSS encoding in base and BSS in candidate; row-count, logical-schema,
and SQL result checks passed. The expected and returned `sum(greptime_value)`
was `9,784,470,159,360` for both targets.
was `9,784,470,159,360` for both targets. This verifies counts and aggregate-query
results, not an exhaustive row-by-row comparison. Base chunks used dictionary
encoding; candidate chunks used BSS without dictionaries, so this is not a
codec-only comparison with dictionary policy held constant. The bytes below
exclude WAL, indexes, metadata, and internal-table storage.
| Fresh run | Base SST bytes | Candidate SST bytes | Candidate change |
| --- | ---: | ---: | ---: |