Skip to content

Commit 08eb6d9

Browse files
committed
Update _async_inserts.md
1 parent 3148918 commit 08eb6d9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/best-practices/_snippets/_async_inserts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ The behavior of asynchronous inserts is further refined using the [`wait_for_asy
2727

2828
When set to 1 (the default), ClickHouse only acknowledges the insert after the data is successfully flushed to disk. This ensures strong durability guarantees and makes error handling straightforward: if something goes wrong during the flush, the error is returned to the client. This mode is recommended for most production scenarios, especially when insert failures must be tracked reliably.
2929

30-
[Benchmarks](https://clickhouse.com/blog/asynchronous-data-inserts-in-clickhouse) show it scales well with concurrency—whether you're running 200 or 500 clients- thanks to adaptive inserts and stable part creation behavior.
30+
[Benchmarks](https://clickhouse.com/blog/asynchronous-data-inserts-in-clickhouse) show it scales well with concurrency—whether you're running 200 or 500 clientsthanks to adaptive inserts and stable part creation behavior.
3131

3232
Setting `wait_for_async_insert = 0` enables "fire-and-forget" mode. Here, the server acknowledges the insert as soon as the data is buffered, without waiting for it to reach storage.
3333

0 commit comments

Comments
 (0)