From 675099b7dcc7dbd2b30ae070490b0f3a6a69ec6d Mon Sep 17 00:00:00 2001 From: Christopher Zell Date: Fri, 16 Aug 2024 15:44:35 +0200 Subject: [PATCH] docs: truncate posts To not have the full blog view on the overview page truncate the blog posts --- .../index.md | 1 + .../index.md | 1 + 2 files changed, 2 insertions(+) diff --git a/chaos-days/blog/2024-07-25-Using-flow-control-to-handle-bottlenecked-exporting/index.md b/chaos-days/blog/2024-07-25-Using-flow-control-to-handle-bottlenecked-exporting/index.md index 7cbb7b8c6..1c2301c89 100644 --- a/chaos-days/blog/2024-07-25-Using-flow-control-to-handle-bottlenecked-exporting/index.md +++ b/chaos-days/blog/2024-07-25-Using-flow-control-to-handle-bottlenecked-exporting/index.md @@ -20,6 +20,7 @@ In these experiments, we will test both ways of limiting the write rate and obse Both setting a static write rate limit and enabling throttling of the write rate can be used to prevent building up an excessive exporting backlog. For users, this will be seen as backpressure because processing speed is limited by the rate at which it can write processing results. + ## Static write limit We will construct a cluster under normal utilization and then artificially degrade the exporting process. diff --git a/chaos-days/blog/2024-07-25-Using-flow-control-to-handle-uncontrolled-process-loops/index.md b/chaos-days/blog/2024-07-25-Using-flow-control-to-handle-uncontrolled-process-loops/index.md index 072188644..3b5698436 100644 --- a/chaos-days/blog/2024-07-25-Using-flow-control-to-handle-uncontrolled-process-loops/index.md +++ b/chaos-days/blog/2024-07-25-Using-flow-control-to-handle-uncontrolled-process-loops/index.md @@ -27,6 +27,7 @@ Enabling the write rate limiting can help mitigate the effects caused by process instances that contain uncontrolled loops by preventing building up an excessive exporting backlog. + ## Mitigating the performance impacts of deployed loops: When an uncontrolled loop is accidentally deployed this tends to use of