From dcd2ad054eea645fbad688c5022362d3f96d85d8 Mon Sep 17 00:00:00 2001 From: Ramon Smits Date: Mon, 4 Nov 2024 17:50:05 +0100 Subject: [PATCH 1/2] SC to use pre-allocated SSD disks and not dynamically allocated virtual disks --- servicecontrol/servicecontrol-instances/hardware.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/servicecontrol/servicecontrol-instances/hardware.md b/servicecontrol/servicecontrol-instances/hardware.md index e1ed32e3cb1..9bd5ea71bc9 100644 --- a/servicecontrol/servicecontrol-instances/hardware.md +++ b/servicecontrol/servicecontrol-instances/hardware.md @@ -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). ### Scaling ServiceControl @@ -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) +* Use of Solid State Drives 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). From 75959f0afe5ae372af22d59b886c4a041e3f94e5 Mon Sep 17 00:00:00 2001 From: Mauro Servienti Date: Thu, 5 Dec 2024 16:50:39 +0100 Subject: [PATCH 2/2] Apply suggestions from code review Co-authored-by: Adam Wright --- servicecontrol/servicecontrol-instances/hardware.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/servicecontrol/servicecontrol-instances/hardware.md b/servicecontrol/servicecontrol-instances/hardware.md index 9bd5ea71bc9..4d846143640 100644 --- a/servicecontrol/servicecontrol-instances/hardware.md +++ b/servicecontrol/servicecontrol-instances/hardware.md @@ -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, 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 @@ -30,8 +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) -* Use of Solid State Drives to significantly reduce seek times and increase throughput +* Use fixed-size (not dynamically expanding virtual) disks +* 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).