Skip to content
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

Jump to bottom

SC to use pre-allocated SSD disks and not dynamically allocated virtual disks #6890

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

SC to use pre-allocated SSD disks and not dynamically allocated virtual disks #6890

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
4 changes: 3 additions & 1 deletion servicecontrol/servicecontrol-instances/hardware.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ This article provides recommendations and performance benchmarks to help select
* A dedicated production server for installing ServiceControl instances (Error, Audit, and Monitoring).
* A minimum of 16 GB of RAM (excluding RAM for OS and other services).
* 2 GHz quad core CPU or better.
* A dedicated disk for ServiceControl databases (not the disk where the operating system is installed).
* A dedicated, non-virtual, pre-allocated disk SSD for ServiceControl databases (not the disk where the operating system is installed).
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
* A dedicated, non-virtual, pre-allocated disk SSD for ServiceControl databases (not the disk where the operating system is installed).
* A dedicated, non-virtual, pre-allocated SSD for ServiceControl databases (not the disk where the operating system is installed).


### Scaling ServiceControl

Expand All @@ -30,6 +30,8 @@ Disk, CPU, RAM, and network performance may be monitored using the Windows Resou
* Store multiple ServiceControl databases on separate physical disks to prevent multiple instances competing for the same disk resources.
* Disable disk write caching (read caching can remain enabled) to prevent data corruption if the (virtual) server or disk controller fails. This is a general best practice for databases.
* [Database paths](/servicecontrol/servicecontrol-instances/configuration.md#embedded-database-servicecontroldbpath) should be located on disks suitable for low latency write operations (e.g. fiber, solid state drives, raid 10), with a recommended IOPS of at least 7500.
* Pre-allocated (not a dynamically expanding virtual disk)
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
* Pre-allocated (not a dynamically expanding virtual disk)
* Use fixed-size (not dynamically expanding virtual) disks

* Use of Solid State Drives to significantly reduce seek times and increase throughput
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
* Use of Solid State Drives to significantly reduce seek times and increase throughput
* Use solid state drives (SSDs) to significantly reduce seek times and increase throughput


> [!NOTE]
> To measure disk performance, use a storage benchmark tool such as Windows System Assessment Tool (`winsat disk -drive g`), [CrystalDiskMark](https://crystalmark.info/en/software/crystaldiskmark/), or [DiskSpd](https://github.com/Microsoft/diskspd).
Expand Down