![]() ![]() 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.Create a Nightly Optimization job that run at 7:00 PM with high priority and all the CPUs and memory available on the system.Remove the currently scheduled Garbage Collection and Integrity Scrubbing Jobs.Disable the scheduled hourly Optimization Jobs.I like their example where Dedup is scheduled to run during off-peak hours on weekends and weeknights after 7:00 PM with a maximum duration of 11 hours. So, how can we tune this? It is pretty easy, and Microsoft has given us an example in the following document of how to strip out the default jobs and recreate them with your default settings. So in your designs, you may want to consider tweaking these values if you find you are having issues. From an architecture perspective, this could be quite problematic because if we need to drain roles off systems while deduplication jobs are running, there might not be enough free RAM to perform the live migrations. I think it is a fair statement to say that with Deduplication enabled your performance penalty will vary depending on how much available RAM is left on the system. Lastly, the 4 node hybrid S2D Cluster didn’t have many VM’s running on it and had 85 % free. The other production all flash S2D 4 node cluster had about 35 % free. The two node S2D Cluster only had 20 % available memory left free on each node. This is why our results were varying above with the performance penalty. Get-dedupschedule | select Type,Priority,Inputoutputthrottlelevel,days,cores,duration,enabled,faststart,full,idletimeout,inputoutputthrottle,memory,name,readonly,scheduledtask | out-gridviewĪs you can see we are going to consume all of the available CPU Cores and up to 50 % of the available memory on the system. To view the default settings in Windows Server 2019, you can run the following: We can see that there is a performance penalty for Deduplication though. I’m going to have to confirm with Microsoft about the actual calculation as there is nothing posted online about this. So, from what I can tell based on my observations the total amount of RAM that is consumed appears to be based on how many drives in the system + number of CSV’s. (As you can see 78186 MB Max memory and 32 Cores) with 8 x CSV’s Here is what a 4-node S2D Cluster all nodes with 16 x 2TB NVME (Journal) and 96 10TB HDD Drives looks like: (As you can see 31416 MB Max memory and 24 Cores) with 4 x CSV’s ![]() Here is what a 4-node S2D Cluster all nodes with 17 x 2TB NVME SSD Drives looks like: (As you can see a 3009 MB Max memory and 4 Cores) with 2 x CSV’s Here is what a 2-node S2D Cluster both nodes with 2 x 2TB NVME SSD Drives looks like: This log shows the maximum amount of RAM, that was used during the deduplication job. Specifically, you want to watch for EVENT ID 10240. Microsoft-Windows-Deduplication/ScrubbingĪs jobs are running, you can check historical statistics about them. ![]() Microsoft-Windows-Deduplication/Diagnostic $DedupDiagevents = Get-WinEvent -Ma圎vents 10 -LogName Microsoft-Windows-Deduplication/Scrubbing | Select-Object * $Dedupevents = Get-WinEvent -Ma圎vents 10 -LogName Microsoft-Windows-Deduplication/Diagnostic | Select-Object * $DedupVolumeStats = Get-dedupvolume D: | Select * $DedupStatus = Get-DedupStatus | Select-Object * These logs carry essential information especially with historical job statistics on Deduplication. The first thing that you need to understand is the Event Logs that capture information about Deduplication. Don’t get me wrong I love this feature and think that it is one of the best in Windows Server 2019 however, you must have an understanding of what it is that you are configuring. Nothing in life is free, and this is certainly the case for Deduplication. Today, I want to talk to you about the performance penalty that is required to run Deduplication on Windows Server 2019. In the previous post, we talked about the essential operator’s report for Storage Spaces Direct in Windows Server 2019. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |