diff --git a/README.md b/README.md index 17d2881..a4895e1 100644 --- a/README.md +++ b/README.md @@ -26,7 +26,7 @@ rerun it and check every figure a post cites. |---|---|---| | [`pattern-identity/`](pattern-identity/) | Does a log line keep the same name over time, and does it get the same name in two places? A four-line replay inside one Drain3 process, two Drain3 instances fed disjoint halves of one stream and two engine 1.1.142 instances fed the same halves, the template string separated from the integer Drain returns beside it, and engine-side coverage probed with invented vocabulary and two LogHub log sets. | Current. Behind *A log pattern name learned from traffic changes as more lines arrive* (draft). | | [`otel-denominators/`](otel-denominators/) | A reduction figure is quoted against a denominator. What happens to it when the denominator changes? One Kubernetes capture measured three ways: as captured, with our own injected field and the collector's debug output removed, and on the log message text alone with the envelope discarded. | Current. Behind the OTel figures in [*Log compaction, measured*](https://www.log10x.com/blog/log-compaction-measured/). | -| [`clickhouse-inflate/`](clickhouse-inflate/) | What does it cost to expand compacted logs at query time in ClickHouse, and what did an earlier Log10x benchmark actually measure? | Current. Behind [*We published a ClickHouse benchmark that measured nothing*](https://www.log10x.com/blog/). | +| [`clickhouse-inflate/`](clickhouse-inflate/) | What does it cost to expand compacted logs at query time in ClickHouse, and what did an earlier Log10x benchmark actually measure? | Current. Behind [*We published a ClickHouse benchmark that measured nothing*](https://www.log10x.com/blog/clickhouse-offload-merge-table/). | | [`clickhouse-clickstack/`](clickhouse-clickstack/) | What does the compact form cost or save on disk in ClickHouse's own recommended log schema, the ClickStack `otel_logs` table, rather than in a single `String` column? Three arms so the row-count change from multi-line folding never hides inside a ratio, three codecs, and a check on whether the compact rows read back as the text they came from. | Current. Not behind a post. | | [`clickstack-e2e/`](clickstack-e2e/) | Does the whole ClickHouse route work end to end, in containers? The released capture through a collector into the 10x receiver, the rows the receiver marked `offload` written to an object store and the rest inserted by ClickStack's own exporter, both sides read back as one table, the query shapes timed with their object-store requests, and a reconciliation of what left the receiver against what is stored. | Current. Behind [*Reading ClickHouse logs from the table and the bucket in one query*](https://www.log10x.com/blog/clickhouse-offload-merge-table/). | | [`clickstack-e2e-gaps/`](clickstack-e2e-gaps/) | The six questions the end to end run left open, each over the whole capture: what a day predicate prunes across thirty days of objects, whether Vector can write the cold branch, whether the Retriever indexes and queries that layout, what a container killed mid-stream costs line by line, which dashboard answers change when rows leave the hot table, and how the per-type policy compares with a collector-only policy on insert and merge CPU. Plus a second pass on four of them: Vector 0.58.0 writing Parquet beside JSON with the Parquet reader's own counters, a `GROUP BY` and an `ORDER BY ... LIMIT` through the Merge table, the collector configured as its code owners prescribe, the `TTL TO VOLUME 'cold'` alternative costed on the same capture, and ClickHouse issue 116888 demonstrated with its guard. | Current. Not behind a post. | diff --git a/clickhouse-inflate/README.md b/clickhouse-inflate/README.md index c6522a5..84f631a 100644 --- a/clickhouse-inflate/README.md +++ b/clickhouse-inflate/README.md @@ -121,8 +121,8 @@ decode exceeds the cap, the post-fix decode runs in hundreds of milliseconds at `corpus/sample-500.jsonl` is 500 compacted OpenTelemetry-demo Kubernetes log events (the fluentd JSON envelope, with the log line replaced by `~,`), and -`corpus/templates.json` is the 378 templates they decode against. Both are the sample published in -[log-10x/clickhouse-app](https://github.com/log-10x/clickhouse-app) under `demo/sample/`, produced +`corpus/templates.json` is the 378 templates they decode against. Both are the sample from +log-10x/clickhouse-app under `demo/sample/`, produced by the 10x engine from the OpenTelemetry demo's container logs. Checksums in `corpus/SHA256SUMS`. `run.sh` cycles that sample to **137,418 rows**, the row count of the table in the post. Cycling