Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
542 changes: 542 additions & 0 deletions content/blog/release-0.9.0.mdx

Large diffs are not rendered by default.

3 changes: 3 additions & 0 deletions scripts/diagram-text.mjs
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,9 @@
const SITE = "https://iggy.apache.org";

export const DIAGRAM_TEXT = {
Bench090DurabilityChart: `**Chart: Replicated vs. Persisted.** Side-by-side panels compare the 0.9.0 release and the next-version development snapshot. Each panel shows Replicated and Persisted producer latency on the same linear scale starting at zero. Controls select single node or 3-node cluster and p50, p99 or p999. All four measurements use 20 pinned producers with an aggregate rate limit of 800 MB/s. Replicated waits for quorum commit and local application. Persisted also requires recoverable stable-storage copies at the quorum. The full measurements appear in the expandable tables below.`,
Bench090LatencyChart: `**Chart: latency, 0.9.0 versus a development snapshot, per iggy-bench workload.** Three headline tiles (3-node cluster, persisted, 20 producers at p999 and p99, and single node, 20 producers at p999), then an interactive chart limited to workloads with lower p50, p99 and p999 latency, with two dots per row on a log scale, one for the 0.9.0 release and one for the development branch that follows it. It switches between single node and 3-node cluster, between p50, p99 and p999, and between table order and biggest percentage reduction. Each version uses its own iggy-bench client. The expandable “Full benchmark results” section below contains all measurements, including regressions and achieved throughput.`,

AppendOnlyLogViz: `**Diagram: Append-only log.** Messages are appended in order, each with the next offset (0, 1, 2 and so on). New messages are always written at the end. A consumer tracks its own position in the log with an offset, independently of other consumers.`,

BenchmarkChart: `**Diagram: Latency improvements, Tokio vs thread-per-core.** Selected historical results comparing v0.5.0 (Tokio) with v0.7.0 (thread-per-core) at about 1,000 MB/s per node. Lower latency is better.
Expand Down
2 changes: 1 addition & 1 deletion scripts/generate-docs-markdown.mjs
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ function transformBody(source, body) {
return line;
}
if (inFence) return line;
const component = /^\s*<([A-Z][A-Za-z]*)\s*\/>\s*$/.exec(line);
const component = /^\s*<([A-Z][A-Za-z0-9]*)\s*\/>\s*$/.exec(line);
if (component) {
const text = DIAGRAM_TEXT[component[1]];
if (!text) {
Expand Down
1 change: 1 addition & 0 deletions src/app/global.css
Original file line number Diff line number Diff line change
Expand Up @@ -129,6 +129,7 @@ figure.shiki {
border-radius: 0.375rem;
padding: 0.15em 0.4em;
font-size: 0.875em;
overflow-wrap: anywhere;
}

.fd-prose a {
Expand Down
Loading
Loading