SC to use pre-allocated SSD disks and not dynamically allocated virtual disks #6890
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mauroservienti
approved these changes
Nov 4, 2024
| @@ -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). | |||
There was a problem hiding this comment.
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). |
awright18
reviewed
Nov 4, 2024
| @@ -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 | |||
There was a problem hiding this comment.
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 |
| @@ -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) | |||
There was a problem hiding this comment.
Suggested change
| * Pre-allocated (not a dynamically expanding virtual disk) | |
| * Use fixed-size (not dynamically expanding virtual) disks |
saratry
approved these changes
Nov 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.