Skip to content

Commit 0eece2a

Browse files
committed
Acrolinx fixes
1 parent 8cb9aa8 commit 0eece2a

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

support/windows-server/backup-and-storage/troubleshoot-performance-issues-storage-spaces-direct.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ Several factors can lead to performance issues for Storage Spaces. The following
3131

3232
- **Incorrect drive configuration**: Using mismatched or incompatible drives within a storage pool can degrade performance.
3333
- **Incorrect storage space type**: Selecting the wrong resiliency option (such as parity instead of simple or mirror) for the workload.
34-
- **Insufficient system resources**: Low memory or CPU availability, which can bottleneck performance.
34+
- **Insufficient system resources**: Low memory or CPU availability that can cause performance bottlenecks.
3535
- **Fragmentation**: Excessive fragmentation within the storage pool can slow down data access.
3636
- **Firmware and driver issues**: Outdated or incompatible drive firmware and drivers.
3737
- **Background tasks**: Resource-intensive background tasks, such as disk scrubbing or repair jobs.
@@ -43,18 +43,18 @@ Follow the steps in this section to improve the performance of your storage spac
4343
Before you start troubleshooting performance issues, consider measuring the system's current performance to establish a baseline. You can use tools such as Performance Monitor or Resource Monitor to collect metrics. You can also use third-party tools such as DiskSpd or CrystalDiskMark to run benchmark tests and gather detailed performance metrics.
4444

4545
> [!IMPORTANT]
46-
> Before you start changing your storage space configuration, make sure that all the storage space's data and configuration settings are backed up.
46+
> Before you start changing your storage space configuration, make sure that the storage space's data and configuration settings are backed up.
4747
4848
### Step 1: Collect performance metrics, events, and configuration information
4949

50-
To assist in troubleshooting, collect the following data:
50+
Collect the following data to help you identify issues:
5151

5252
- A detailed description of the storage space configuration, including the resiliency type and drive details.
5353
- What type of storage space configuration is being used? For example, simple, mirror, or parity?
5454
- What is the size of the storage pool, and how many drives are included?
5555
- What is the current firmware and driver version for the drives in the storage pool?
5656
- Are all drives in the pool of the same type, capacity, and speed?
57-
- Have there been any recent changes to the system, such as software updates, hardware replacements, or new applications installed?
57+
- Are any recent changes to the system, such as software updates, hardware replacements, or new applications installed?
5858
- Information about recent system updates or changes.
5959

6060
- Performance metrics, such as disk queue length and throughput. You can use tools such as Performance Monitor or Task Manager to collect this information. You can also review performance history information, as described in [Performance history for Storage Spaces Direct](/windows-server/storage/storage-spaces/performance-history).
@@ -72,7 +72,7 @@ To assist in troubleshooting, collect the following data:
7272

7373
### Step 2: Verify the Storage Space configuration
7474

75-
1. Make sure that all the drives in the pool are of the same type (for example, all SSDs or all HDDs) and have similar performance characteristics.
75+
1. Make sure that all the drives in the pool are of the same type (for example, all solid-state drives (SSDs) or all hard disk drives (HDDs)) and have similar performance characteristics.
7676
1. Check that the storage space type (simple, mirror, or parity) is appropriate for the workload. For more information about storage space types in S2D, see [Deep Dive: Volumes in Storage Spaces Direct](https://techcommunity.microsoft.com/blog/filecab/deep-dive-volumes-in-storage-spaces-direct/425807).
7777
1. If you make any changes during this step, test the system's performance and compare it to earlier measurements.
7878

@@ -91,7 +91,7 @@ To assist in troubleshooting, collect the following data:
9191

9292
### Step 5: Run storage maintenance tasks
9393

94-
1. To optimize the storage pool, run the following cmdlet at a powerShell command prompt:
94+
1. To optimize the storage pool, run the following cmdlet at a PowerShell command prompt:
9595

9696
```powershell
9797
Optimize-StoragePool -FriendlyName <StoragePoolName>
@@ -115,7 +115,7 @@ To assist in troubleshooting, collect the following data:
115115

116116
### Step 7: Rebuild or recreate the storage space
117117

118-
If you followed the earlier steps and the S2D performance hasn't improved sufficiently, consider rebuilding the storage space. Follow these steps:
118+
If you followed the earlier steps and the S2D performance didn't improve sufficiently, consider rebuilding the storage space. Follow these steps:
119119

120120
1. Make sure that all backups are current and available.
121121
1. Delete the existing storage space.

0 commit comments

Comments
 (0)