From 6448be2c74d25c6ba9eab40fe38bdc9f08ede7be Mon Sep 17 00:00:00 2001 From: Jason Stirnaman Date: Wed, 5 Mar 2025 16:54:17 -0600 Subject: [PATCH] Update content/shared/v3-core-get-started/_index.md --- content/shared/v3-core-get-started/_index.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/shared/v3-core-get-started/_index.md b/content/shared/v3-core-get-started/_index.md index 180b4ff61..d2c1d8ce3 100644 --- a/content/shared/v3-core-get-started/_index.md +++ b/content/shared/v3-core-get-started/_index.md @@ -329,8 +329,9 @@ For more information, see [diskless architecture](#diskless-architecture). > [!Note] > ##### Write requests return after WAL flush > -> By default, when you write data, InfluxDB sends a write response after the WAL file has been flushed to the Object store (default is every second). Write requests might not complete quickly, but you can make many concurrent requests to achieve higher total throughput. -For faster write responses, you can use the [`no_sync` option](#no-sync-write-option) to skip the wait for WAL persistence. +> By default, InfluxDB acknowledges writes after flushing the WAL file to the Object store (occurring every second). For high throughput, you can send multiple concurrent write requests. +> +> To reduce the latency of writes, use the [`no_sync` write option](#no-sync-write-option), which acknowledges writes _before_ WAL persistence completes. ##### No sync write option