From 389cc94e26aba997926fe176414040ec62d45395 Mon Sep 17 00:00:00 2001 From: Christopher Zell Date: Mon, 19 Aug 2024 16:46:41 +0200 Subject: [PATCH] fix: typo --- .../blog/2024-08-19-Operate-improve-import-latency/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/chaos-days/blog/2024-08-19-Operate-improve-import-latency/index.md b/chaos-days/blog/2024-08-19-Operate-improve-import-latency/index.md index 2c0a6f6cb..5c8875bfe 100644 --- a/chaos-days/blog/2024-08-19-Operate-improve-import-latency/index.md +++ b/chaos-days/blog/2024-08-19-Operate-improve-import-latency/index.md @@ -218,9 +218,9 @@ Looking into it further, the backpressure is not affected by the newest feature ![higher-load-less-throughput-commit-latency](higher-load-less-throughput-commit-latency.png) -The slower benchmark, seem to have a degraded commit latency, which in consequence slows down the whole system. It is unclear right now, which this is. +The slower benchmark, seem to have a degraded commit latency, which in consequence slows down the whole system. It is unclear right now, why this is. -The fast benchmark, with the configured exporting, has a much better commit latency. It is unlikely that this configuration affected this part of the system. We will have to retry the both benchmarks. +The faster benchmark, with the configured exporting, has a much better commit latency. It is unlikely that the exporter configuration affected this part of the system. We will have to retry the both benchmarks. ![higher-load-higher-throughput](higher-load-higher-throughput-commit-latency.png)