diff --git a/modules/learn/pages/buckets-memory-and-storage/storage-settings.adoc b/modules/learn/pages/buckets-memory-and-storage/storage-settings.adoc
index c28604e470..233d3b50c7 100644
--- a/modules/learn/pages/buckets-memory-and-storage/storage-settings.adoc
+++ b/modules/learn/pages/buckets-memory-and-storage/storage-settings.adoc
@@ -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.
 
+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.
diff --git a/modules/manage/pages/manage-settings/general-settings.adoc b/modules/manage/pages/manage-settings/general-settings.adoc
index 5eed55fbee..833da56fb5 100644
--- a/modules/manage/pages/manage-settings/general-settings.adoc
+++ b/modules/manage/pages/manage-settings/general-settings.adoc
@@ -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.