You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/shared/v3-core-get-started/_index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -332,7 +332,7 @@ InfluxDB provides a `no_sync` write option that allows the write request to resp
332
332
333
333
Using `no_sync=true` is best when prioritizing high-throughput writes over absolute durability.
334
334
335
-
- Default behavior(`no_sync=false`): Ensures data is persisted before acknowledging writes. Thus, reducing the risk of data loss.
335
+
- Default behavior(`no_sync=false`): Waits fordata to be written to disk before acknowledging writes. This reduces the risk of data loss but increases latency for writes.
336
336
- With `no_sync=true`: Improves write performance but increases the risk of data loss incase of crashes before WAL persistence.
337
337
338
338
If you are using the HTTP API, here is an example of how to enable the `no_sync` option:
0 commit comments