DataDestageSsdFillRatioThreshold equivalent for Windows 10 NTFS

[i3v]

This a nice article briefly explains how "destaging" works for ReFS on Windows Server and how to use the DataDestageSsdFillRatioThreshold. However, there seem to be no equivalent documentation for NTFS on Windows 10.

As far as I understand, in this case, "destaging" only happens during either Optimize-Volume -DriveLetter H -TierOptimize or defrag.exe /C /H /K /G. However, it is not documented, what "FillRatio" this optimization would achieve and how to adjust it.

This is an important aspect, because the empty space on the Performance Tier effectively serves as the write cache for the burst writes, and user might want to optimize the system for a particular known size of such a "burst write".

Also, it would also make sense to explain the data writing strategy - if all data is written the the Performance tier if there's enough space there. When WriteCache is used "only for small files that should be written to Capacity tier because there's no space left on the Perfomance tier", maybe?

Few related discussions: 1, 2.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 198ff551-d313-df0e-a0f8-de49be2cb4dc
• Version Independent ID: 26372edb-c31a-9683-1d60-07c891fe65ee
• Content: Optimize-Volume (Storage)
• Content Source: docset/winserver2019-ps/storage/Optimize-Volume.md
• Product: w10
• Technology: windows
• GitHub Login: @JasonGerend
• Microsoft Alias: jgerend

[officedocspr5]

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.

As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.

If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.

With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.

Here's what the new experience looks like.

Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.

First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful	Article was unhelpful

Finally, select Submit and you're done!