Skip to content

Doc 9868 76 b #3973

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: release/7.6
Choose a base branch
from
Open

Doc 9868 76 b #3973

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions modules/learn/pages/buckets-memory-and-storage/storage-settings.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,8 @@ The maximum thread-allocation that can be specified for each is _64_, the minimu
A high thread-allocation may improve performance on systems whose hardware resources are commensurately supportive, (for example, where the number of CPU cores is high).
In particular, a high number of _writer_ threads on such systems may significantly optimize the performance of _durable writes: see xref:learn:data/durability.adoc[Durability], for information.
Copy link
Contributor

@RichardSmedley RichardSmedley Nov 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like the missing _ is leaving the next few lines as italic?

Copy link
Contributor

@RichardSmedley RichardSmedley Nov 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or maybe not - view page doesn't show it. 🤷

Copy link
Contributor

@rao-shwe rao-shwe Nov 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
In particular, a high number of _writer_ threads on such systems may significantly optimize the performance of _durable writes: see xref:learn:data/durability.adoc[Durability], for information.
In particular, a high number of _writer_ threads on such systems may significantly optimize the performance of _durable writes_: see xref:learn:data/durability.adoc[Durability], for information.


A high number of reader and writer threads will benefit disk based workloads that require high throughput especially when using high end disk drives such as NVMe SSDs. This is likely to be the case when using Magma as the storage engine. In this case it is best to choose xref:manage:manage-settings/general-settings.adoc#data-settings['Disk i/o optimized'] mode for Reader and Writer thread settings.

Note, however, that a high thread-allocation might _impair_ some aspects of performance on less appropriately resourced nodes.
Consequently, changes to the default thread-allocation should not be made to production systems without prior testing.
A starting-point for experimentation is to establish the numbers for reader threads and writer threads as each equal to the _queue depth_ of the underlying I/O subsystem.
Expand Down
2 changes: 2 additions & 0 deletions modules/manage/pages/manage-settings/general-settings.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,6 +163,8 @@ The maximum thread-allocation to each is _64_, the minimum _4_.
A high thread-allocation may improve performance on systems whose hardware-resources are commensurately supportive (for example, where the number of CPU cores is high).
In particular, a high number of _writer_ threads on such systems may significantly optimize the performance of _durable writes_: see xref:learn:data/durability.adoc[Durability], for information.

A high number of reader and writer threads will benefit disk based workloads that require high throughput especially when using high end disk drives such as NVMe SSDs. This is likely to be the case when using Magma as the storage engine. In this case it is best to choose xref:manage:manage-settings/general-settings.adoc#data-settings['Disk i/o optimized'] mode for Reader and Writer thread settings.

Note, however, that a high thread-allocation might _impair_ some aspects of system-performance on less appropriately resourced nodes.
Consequently, changes to the default thread-allocation should not be made to production systems without prior testing.

Expand Down
Loading