進階重複資料刪除設定Advanced Data Deduplication settings

適用於 Windows Server (半年度管道)、Windows Server 2016Applies to Windows Server (Semi-Annual Channel), Windows Server 2016

本文件說明如何修改進階重複資料刪除設定。This document describes how to modify advanced Data Deduplication settings. 針對建議的工作負載,預設設定應已足夠。For recommended workloads, the default settings should be sufficient. 修改這些設定的主要原因,是為了改進重複資料刪除搭配其他工作負載類型時的效能。The main reason to modify these settings is to improve Data Deduplication's performance with other kinds of workloads.

修改重複資料刪除工作排程Modifying Data Deduplication job schedules

預設重複資料刪除工作排程是專為搭配建議的工作負載運作並盡可能不干擾工作而設計 (不包括為備份使用類型啟用的「優先順序最佳化」工作)。The default Data Deduplication job schedules are designed to work well for recommended workloads and be as non-intrusive as possible (excluding the Priority Optimization job that is enabled for the Backup usage type). 當工作負載有大型資源需求時,它可以確保工作僅在閒置時間執行,或是減少或增加允許重複資料刪除工作使用的系統資源量。When workloads have large resource requirements, it is possible to ensure that jobs run only during idle hours, or to reduce or increase the amount of system resources that a Data Deduplication job is allowed to consume.

變更重複資料刪除排程Changing a Data Deduplication schedule

重複資料刪除工作是透過 Windows 工作排程器排程,並且可以在 Microsoft\Windows\Deduplication 路徑下檢視及編輯。Data Deduplication jobs are scheduled via Windows Task Scheduler and can be viewed and edited there under the path Microsoft\Windows\Deduplication. 重複資料刪除包括數個可讓您輕鬆排程的 Cmdlet。Data Deduplication includes several cmdlets that make scheduling easy.

變更重複資料刪除工作執行時間最常見的原因,是為了確保工作在非尖峰時間執行。The most common reason for changing when Data Deduplication jobs run is to ensure that jobs run during off hours. 以下的逐步範例示範如何針對「陽光普照的一天」案例修改重複資料刪除排程:有一部超交集 Hyper-V 主機會在週末以及工作日下午 7:00 之後閒置。The following step-by-step example shows how to modify the Data Deduplication schedule for a sunny day scenario: a hyper-converged Hyper-V host that is idle on weekends and after 7:00 PM on weeknights. 為了變更排程,請使用系統管理員身分執行下列 PowerShell Cmdlet。To change the schedule, run the following PowerShell cmdlets in an Administrator context.

  1. 停用排定的每小時最佳化工作。Disable the scheduled hourly Optimization jobs.

    Set-DedupSchedule -Name BackgroundOptimization -Enabled $false
    Set-DedupSchedule -Name PriorityOptimization -Enabled $false
    
  2. 移除目前排定的記憶體回收完整性清除工作。Remove the currently scheduled Garbage Collection and Integrity Scrubbing jobs.

    Get-DedupSchedule -Type GarbageCollection | ForEach-Object { Remove-DedupSchedule -InputObject $_ }
    Get-DedupSchedule -Type Scrubbing | ForEach-Object { Remove-DedupSchedule -InputObject $_ }
    
  3. 建立夜間最佳化工作,它會在下午 7:00 執行,具有高優先順序,並使用系統上所有可用的 CPU 和記憶體。Create a nightly Optimization job that runs at 7:00 PM with high priority and all the CPUs and memory available on the system.

    New-DedupSchedule -Name "NightlyOptimization" -Type Optimization -DurationHours 11 -Memory 100 -Cores 100 -Priority High -Days @(1,2,3,4,5) -Start (Get-Date "2016-08-08 19:00:00")
    

    注意

    -Start 提供之 System.Datetime 中的「日期」部分是無關的 (只要是過去的日期即可),但「時間」部分會指定工作應該開始的時間。The date part of the System.Datetime provided to -Start is irrelevant (as long as it's in the past), but the time part specifies when the job should start.

  4. 建立每週的記憶體回收工作,它會在星期六上午 7:00 執行,具有高優先順序,並使用系統上所有可用的 CPU 和記憶體。Create a weekly Garbage Collection job that runs on Saturday starting at 7:00 AM with high priority and all the CPUs and memory available on the system.

    New-DedupSchedule -Name "WeeklyGarbageCollection" -Type GarbageCollection -DurationHours 23 -Memory 100 -Cores 100 -Priority High -Days @(6) -Start (Get-Date "2016-08-13 07:00:00")
    
  5. 建立每週的完整性清除工作,它會在星期日上午 7 時執行,具有高優先順序,並使用系統上所有可用的 CPU 和記憶體。Create a weekly Integrity Scrubbing job that runs on Sunday starting at 7 AM with high priority and all the CPUs and memory available on the system.

    New-DedupSchedule -Name "WeeklyIntegrityScrubbing" -Type Scrubbing -DurationHours 23 -Memory 100 -Cores 100 -Priority High -Days @(0) -Start (Get-Date "2016-08-14 07:00:00")
    

可用的全工作設定Available job-wide settings

您可以針對新的或是排定的重複資料刪除工作切換下列設定:You can toggle the following settings for new or scheduled Data Deduplication jobs:

參數名稱Parameter name 定義Definition 接受的值Accepted values 為何要設定此值?Why would you want to set this value?
類型Type 應排定的工作類型The type of the job that should be scheduled
  • OptimizationOptimization
  • GarbageCollectionGarbageCollection
  • ScrubbingScrubbing
此值為必要,因為它是您要排定的工作類型。This value is required because it is the type of job that you want to have be scheduled. 在工作排定之後,您就無法變更這個值。This value cannot be changed after the task has been scheduled.
優先順序Priority 已排定工作的系統優先順序The system priority of the scheduled job
  • High
  • Medium
  • Low
這個值有助於系統判斷如何配置 CPU 時間。This value helps the system determine how to allocate CPU time. High 將使用較多的 CPU 時間,Low 則會使用較少的 CPU 時間。High will use more CPU time, low will use less.
Days 排定執行工作的日子The days that the job is scheduled 0-6 的整數陣列,代表星期幾:An array of integers 0-6 representing the days of the week:
  • 0 = 星期日0 = Sunday
  • 1 = 星期一1 = Monday
  • 2 = 星期二2 = Tuesday
  • 3 = 星期三3 = Wednesday
  • 4 = 星期四4 = Thursday
  • 5 = 星期五5 = Friday
  • 6 = 星期六6 = Saturday
排定的工作必須至少在其中一天執行。Scheduled tasks have to run on at least one day.
CoresCores 工作應使用系統上之核心的百分比The percentage of cores on the system that a job should use 整數 0-100 (表示百分比)Integers 0-100 (indicates a percentage) 控制工作將對系統上的計算資源產生的影響程度To control what level of impact a job will have on the compute resources on the system
DurationHoursDurationHours 允許工作執行的時數上限The maximum number of hours a job should be allowed to run 正整數Positive integers 避免工作和工作負載的非閒置時間強碰To prevent a job for running into a workload's non-idle hours
啟用Enabled 是否將執行工作Whether the job will run True/falseTrue/false 停用工作而不移除工作To disable a job without removing it
完整Full 用於排程完整記憶體回收工作For scheduling a full Garbage Collection job 參數 (true/false)Switch (true/false) 根據預設,每第四個工作為完整記憶體回收工作。By default, every fourth job is a full Garbage Collection job. 使用此參數,您就可以排程完整記憶體回收以更頻繁地執行。With this switch, you can schedule full Garbage Collection to run more frequently.
InputOutputThrottleInputOutputThrottle 指定套用至工作的輸出/輸入量節流設定Specifies the amount of input/output throttling applied to the job 整數 0-100 (表示百分比)Integers 0-100 (indicates a percentage) 節流設定可確保工作不會干擾其他進行大量 I/O 的程序。Throttling ensures that jobs don't interfere with other I/O-intensive processes.
MemoryMemory 系統上工作應使用之記憶體的百分比The percentage of memory on the system that a job should use 整數 0-100 (表示百分比)Integers 0-100 (indicates a percentage) 控制工作將對系統上的記憶體資源產生的影響程度To control what level of impact the job will have on the memory resources of the system
名稱Name 已排程工作的名稱The name of the scheduled job StringString 工作必須有可唯一識別的名稱。A job must have a uniquely identifiable name.
ReadOnlyReadOnly 指示清除工作程序,並報告它所發現的損毀,但不執行任何修復動作Indicates that the scrubbing job processes and reports on corruptions that it finds, but does not run any repair actions 參數 (true/false)Switch (true/false) 您可以手動還原位於磁碟損壞區段的檔案。You want to manually restore files that sit on bad sections of the disk.
啟動Start 指定工作應該開始的時間Specifies the time a job should start System.DateTime Start 提供之 System.Datetime 中的「日期」部分是無關的 (只要是過去的日期即可),但「時間」部分會指定工作應該開始的時間。The date part of the System.Datetime provided to Start is irrelevant (as long as it's in the past), but the time part specifies when the job should start.
StopWhenSystemBusyStopWhenSystemBusy 指定重複資料刪除是否應該在系統忙碌時停止Specifies whether Data Deduplication should stop if the system is busy 參數 (true/false)Switch (True/False) 這個參數可讓您控制重複資料刪除的行為--如果您想要在工作負載並非閒置時執行重複資料刪除,這特別重要。This switch gives you the ability to control the behavior of Data Deduplication--this is especially important if you want to run Data Deduplication while your workload is not idle.

修改重複資料刪除全磁碟區設定Modifying Data Deduplication volume-wide settings

切換磁碟區設定Toggling volume settings

您可以透過在啟用磁碟區重複資料刪除時所選取的使用類型,來設定全磁碟區預設設定。You can set the volume-wide default settings for Data Deduplication via the usage type that you select when you enable a deduplication for a volume. 重複資料刪除包括可輕鬆編輯全磁碟區設定的 Cmdlet:Data Deduplication includes cmdlets that make editing volume-wide settings easy:

從所選使用類型修改磁碟區設定的主要原因,是為了改進特定檔案 (例如多媒體或其他已壓縮的檔案類型) 的讀取效能,或微調重複資料刪除以針對您的特定工作負載達到更好的最佳化。The main reasons to modify the volume settings from the selected usage type are to improve read performance for specific files (such as multimedia or other file types that are already compressed) or to fine-tune Data Deduplication for better optimization for your specific workload. 下列範例示範如何針對最類似於一般用途檔案伺服器工作負載,但使用經常變更之大型檔案的工作負載,修改重複資料刪除磁碟區設定。The following example shows how to modify the Data Deduplication volume settings for a workload that most closely resembles a general purpose file server workload, but uses large files that change frequently.

  1. 查看叢集共用磁碟區 1 的目前磁碟區設定。See the current volume settings for Cluster Shared Volume 1.

    Get-DedupVolume -Volume C:\ClusterStorage\Volume1 | Select *
    
  2. 啟用叢集共用磁碟區 1 上的 OptimizePartialFiles,讓 MinimumFileAge 原則套用至檔案的區段,而非整個檔案。Enable OptimizePartialFiles on Cluster Shared Volume 1 so that the MinimumFileAge policy applies to sections of the file rather than the whole file. 這樣可確保即使檔案的區段經常變更,檔案的大部分仍可獲得最佳化。This ensures that the majority of the file gets optimized even though sections of the file change regularly.

    Set-DedupVolume -Volume C:\ClusterStorage\Volume1 -OptimizePartialFiles
    

可用的全磁碟區設定Available volume-wide settings

設定名稱Setting name 定義Definition 接受的值Accepted values 為何要修改此值?Why would you want to modify this value?
ChunkRedundancyThresholdChunkRedundancyThreshold 區塊在複製到區塊存放區的熱點區段之前,區塊被參考的次數。The number of times that a chunk is referenced before a chunk is duplicated into the hotspot section of the Chunk Store. 熱點區段的值是所謂的「熱門」區塊,經常會被參考,並有多個存取路徑以改善存取時間。The value of the hotspot section is that so-called "hot" chunks that are referenced frequently have multiple access paths to improve access time. 正整數Positive integers 修改此數字的主要原因是為了增加具有高度重複資料磁碟區的儲存速率。The main reason to modify this number is to increase the savings rate for volumes with high duplication. 一般情況下,建議的設定為預設值 (100),且您應該不需要修改這個值。In general, the default value (100) is the recommended setting, and you shouldn't need to modify this.
ExcludeFileTypeExcludeFileType 要在最佳化時排除的檔案類型File types that are excluded from optimization 副檔名的陣列Array of file extensions 某些檔案類型,特別是多媒體或是已壓縮的檔案,最佳化之後並不會有太多好處。Some file types, particularly multimedia or files that are already compressed, do not benefit very much from being optimized. 此設定可讓您設定要排除的類型。This setting allows you to configure which types are excluded.
ExcludeFolderExcludeFolder 指定不應考量進行最佳化的資料夾路徑Specifies folder paths that should not be considered for optimization 資料夾路徑的陣列Array of folder paths 如果您想要改善效能,或是不要讓特定路徑中的內容被最佳化,您可以將磁碟區上的特定路徑排除在最佳化的考量之外。If you want to improve performance or keep content in particular paths from being optimized, you can exclude certain paths on the volume from consideration for optimization.
InputOutputScaleInputOutputScale 指定後續處理工作期間重複資料刪除要在磁碟區上使用的 IO 平行處理層級 (IO 佇列)Specifies the level of IO parallelization (IO queues) for Data Deduplication to use on a volume during a post-processing job 正整數,範圍 1-36Positive integers ranging 1-36 修改此值的主要原因是藉由限制允許重複資料刪除在磁碟區上使用的 IO 佇列數目,減少對高 IO 工作負載的效能影響。The main reason to modify this value is to decrease the impact on the performance of a high IO workload by restricting the number of IO queues that Data Deduplication is allowed to use on a volume. 請注意,修改此設定的預設值,可能會導致重複資料刪除的後續處理工作執行速度變慢。Note that modifying this setting from the default may cause Data Deduplication's post-processing jobs to run slowly.
MinimumFileAgeDaysMinimumFileAgeDays 檔案建立之後,在被視為需要依原則進行最佳化之前的天數。Number of days after the file is created before the file is considered to be in-policy for optimization. 正整數 (包括零)Positive integers (inclusive of zero) 預設HyperV 使用類型會將此值設定為 3,來將熱門或最近所建立檔案的效能最佳化。The Default and HyperV usage types set this value to 3 to maximize performance on hot or recently created files. 如果您想要更積極進行重複資料刪除,或如果您不在意因為重複資料刪除而產生相關聯的額外延遲,您可以修改此值。You may want to modify this if you want Data Deduplication to be more aggressive or if you do not care about the extra latency associated with deduplication.
MinimumFileSizeMinimumFileSize 檔案在被視為需要依原則進行最佳化時的最小檔案大小Minimum file size that a file must have to be considered in-policy for optimization 大於 32 KB的正整數 (位元組)Positive integers (bytes) greater than 32 KB 變更此值的主要原因是為了排除最佳化價值有限的小型檔案,以節省運算時間。The main reason to change this value is to exclude small files that may have limited optimization value to conserve compute time.
NoCompressNoCompress 區塊是否應在放入區塊存放區之前壓縮Whether the chunks should be compressed before being put into the Chunk Store True/FalseTrue/False 某些類型的檔案 (特別是多媒體檔案和已壓縮的檔案類型) 可能無法妥善壓縮。Some types of files, particularly multimedia files and already compressed file types, may not compress well. 此設定可讓您針對磁碟區上的所有檔案關閉壓縮。This setting allows you to turn off compression for all files on the volume. 如果您正在最佳化的資料集包含許多已壓縮的檔案,這會是理想的設定。This would be ideal if you are optimizing a dataset that has a lot of files that are already compressed.
NoCompressionFileTypeNoCompressionFileType 區塊進入區塊存放區之前,其區塊不應被壓縮的檔案類型File types whose chunks should not be compressed before going into the Chunk Store 副檔名的陣列Array of file extensions 某些類型的檔案 (特別是多媒體檔案和已壓縮的檔案類型) 可能無法妥善壓縮。Some types of files, particularly multimedia files and already compressed file types, may not compress well. 此設定可針對那些檔案關閉壓縮,以節省 CPU 資源。This setting allows compression to be turned off for those files, saving CPU resources.
OptimizeInUseFilesOptimizeInUseFiles 啟用時,具有作用中控制代碼的檔案本身會被視為需要依原則進行最佳化。When enabled, files that have active handles against them will be considered as in-policy for optimization. True/falseTrue/false 如果您的工作負載持續開啟檔案很長的時間,請啟用此設定。Enable this setting if your workload keeps files open for extended periods of time. 如果設定沒有啟用,則如果工作負載開啟對檔案的控制代碼,檔案將永遠不會進行最佳化,即使它僅是偶爾在結尾附加資料也一樣。If this setting is not enabled, a file would never get optimized if the workload has an open handle to it, even if it's only occasionally appending data at the end.
OptimizePartialFilesOptimizePartialFiles 啟用時,MinimumFileAge 值會套用至檔案的區段,而非整個檔案。When enabled, the MinimumFileAge value applies to segments of a file rather than to the whole file. True/falseTrue/false 如果您的工作負載會使用大型、經常編輯的檔案,而其中大部分的檔案內容不會更動,請啟用此設定。Enable this setting if your workload works with large, often edited files where most of the file content is untouched. 如果未啟用此設定,即使大部分的檔案內容已準備好最佳化,這些檔案也將永遠不會進行最佳化,因為它們持續在變更。If this setting is not enabled, these files would never get optimized because they keep getting changed, even though most of the file content is ready to be optimized.
驗證Verify 啟用時,如果區塊的雜湊和我們在區塊存放區中已經擁有的區塊相符,就會逐個位元組比較該區塊以確保它們完全相同。When enabled, if the hash of a chunk matches a chunk we already have in our Chunk Store, the chunks are compared byte-by-byte to ensure they are identical. True/falseTrue/false 這是一項完整性功能,可確保比較區塊的雜湊演算法在比較實際上不同但擁有相同雜湊的兩個資料區塊時,不會發生錯誤。This is an integrity feature that ensures that the hashing algorithm that compares chunks does not make a mistake by comparing two chunks of data that are actually different but have the same hash. 實際上,這幾乎不太可能發生。In practice, it is extremely improbable that this would ever happen. 啟用驗證功能會對最佳化工作增加相當大的負擔。Enabling the verification feature adds significant overhead to the optimization job.

修改重複資料刪除全系統設定Modifying Data Deduplication system-wide settings

重複資料刪除有其他的全系統設定,可透過登錄編輯程式來設定。Data Deduplication has additional system-wide settings that can be configured via the registry. 這些設定會套用到在系統上執行的所有工作和磁碟區。These settings apply to all of the jobs and volumes that run on the system. 編輯登錄時,請務必非常小心。Extra care must be given whenever editing the registry.

例如,您可能想要停用完整記憶體回收。For example, you may want to disable full Garbage Collection. 如需關於這為何可能對您的案例有用的詳細資訊,請參閱常見問題集More information about why this may be useful for your scenario can be found in Frequently asked questions. 若要使用 PowerShell 編輯登錄:To edit the registry with PowerShell:

  • 如果重複資料刪除正在叢集中執行:If Data Deduplication is running in a cluster:

    Set-ItemProperty -Path HKLM:\System\CurrentControlSet\Services\ddpsvc\Settings -Name DeepGCInterval -Type DWord -Value 0xFFFFFFFF
    Set-ItemProperty -Path HKLM:\CLUSTER\Dedup -Name DeepGCInterval -Type DWord -Value 0xFFFFFFFF
    
  • 如果重複資料刪除未在叢集中執行:If Data Deduplication is not running in a cluster:

    Set-ItemProperty -Path HKLM:\System\CurrentControlSet\Services\ddpsvc\Settings -Name DeepGCInterval -Type DWord -Value 0xFFFFFFFF
    

可用的全系統設定Available system-wide settings

設定名稱Setting name 定義Definition 接受的值Accepted values 為什麼要變更此值?Why would you want to change this?
WlmMemoryOverPercentThresholdWlmMemoryOverPercentThreshold 此設定可允許工作使用比重複資料刪除判斷的實際可用記憶體量更多的記憶體。This setting allows jobs to use more memory than Data Deduplication judges to actually be available. 例如,設定為 300 表示工作使用的記憶體量必須達到所指派記憶體的三倍,才會取消工作。For example, a setting of 300 would mean that the job would have to use three times the assigned memory to get canceled. 正整數 (300 的值表示 300% 或 3 倍)Positive integers (a value of 300 means 300% or 3 times) 如果您有另一項工作會在重複資料刪除使用更多記憶體時停止If you have another task that will stop if Data Deduplication takes more memory
DeepGCIntervalDeepGCInterval 此設定可設定一般記憶體回收工作變成完整記憶體回收工作的間隔。This setting configures the interval at which regular Garbage Collection jobs become full Garbage Collection jobs. 設定為 n 代表每第 n 次工作將會是完整記憶體回收工作。A setting of n would mean that every nth job was a full Garbage Collection job. 請注意,完整記憶體回收對備份使用類型的磁碟區永遠停用(無論登錄值)。Note that full Garbage Collection is always disabled (regardless of the registry value) for volumes with the Backup Usage Type. Start-DedupJob -Type GarbageCollection -Full 如果需要在備份磁碟區上使用完整記憶體回收,可能使用。may be used if full Garbage Collection is desired on a Backup volume. 整數(-1 指出已停用)Integers (-1 indicates disabled) 請參閱此常見問題集See this frequently asked question

常見問題集Frequently asked questions

我變更了重複資料刪除設定,現在工作速度卻變慢或無法完成,或我的工作負載效能降低。為什麼?I changed a Data Deduplication setting, and now jobs are slow or don't finish, or my workload performance has decreased. Why?
這些設定提供您許多強大的功能來控制重複資料刪除的執行方式。These settings give you a lot of power to control how Data Deduplication runs. 請謹慎使用這些設定,並監視效能Use them responsibly, and monitor performance.

我想要立即執行重複資料刪除工作,但不想建立新的排程--可以這樣做嗎?I want to run a Data Deduplication job right now, but I don't want to create a new schedule--can I do this?
可以,所有的工作均可手動執行Yes, all jobs can be run manually.

完整和一般記憶體回收之間有什麼不同?What is the difference between full and regular Garbage Collection?
記憶體回收有兩種類型:There are two types of Garbage Collection:

  • 「一般記憶體回收」會使用統計演算法來尋找符合特定條件 (記憶體與 IOPS 不足) 的大型未被參考區塊。Regular Garbage Collection uses a statistical algorithm to find large unreferenced chunks that meet a certain criteria (low in memory and IOPs). 一般記憶體回收只有在未被參考區塊的百分比達到下限時,才會壓縮區塊存放區容器。Regular Garbage Collection compacts a chunk store container only if a minimum percentage of the chunks are unreferenced. 相較於完整記憶體回收,此類型記憶體回收的執行速度更快且使用的資源較少。This type of Garbage Collection runs much faster and uses fewer resources than full Garbage Collection. 一般記憶體回收工作的預設排程是一星期執行一次。The default schedule of the regular Garbage Collection job is to run once a week.
  • 「完整記憶體回收」會執行更完整的工作,以尋找未參考區塊並釋放更多磁碟空間。Full Garbage Collection does a much more thorough job of finding unreferenced chunks and freeing more disk space. 完整記憶體回收會壓縮每一個容器,即使容器內只有單一區塊未被參考。Full Garbage Collection compacts every container even if just a single chunk in the container is unreferenced. 如果在最佳化工作期間曾發生當機或電源中斷,完整記憶體回收也會釋放曾經使用的空間。Full Garbage Collection will also free space that may have been in use if there was a crash or power failure during an Optimization job. 完整記憶體回收工作將會 100% 復原重複資料刪除磁碟區上可復原的可用空間,代價則是需要比執行一般記憶體回收工作時更多的時間與系統資源。Full Garbage Collection jobs will recover 100 percent of the available space that can be recovered on a deduplicated volume at the cost of requiring more time and system resources compared to a regular Garbage Collection job. 與一般記體回收工作相比,完整記憶體回收工作通常會尋找並釋放最多多 5% 的額外未被參考資料。The full Garbage Collection job will typically find and release up to 5 percent more of the unreferenced data than a regular Garbage Collection job. 完整記憶體回收工作的預設排程是在每排程四次記憶體回收時執行。The default schedule of the full Garbage Collection job is to run every fourth time Garbage Collection is scheduled.

為什麼要停用完整記憶體回收?Why would I want to disable full Garbage Collection?

  • 記憶體回收可能會對磁碟區的存留期陰影複製和增量備份大小產生不利影響。Garbage Collection could adversely affect the volume's lifetime shadow copies and the size of incremental backup. 執行完整記憶體回收工作時,可能會看到高區塊或 I/O 密集性工作負載的效能降低。High churn or I/O-intensive workloads may see a degradation in performance by full Garbage Collection jobs.
  • 如果您知道系統當機,您可以從 PowerShell 手動執行完整記憶體回收工作來清除流失的部分。You can manually run a full Garbage Collection job from PowerShell to clean up leaks if you know your system crashed.