Skip to content

Fix formatting errors in ReFS memory usage recommendation #2020

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mastercoms wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix formatting errors in ReFS memory usage recommendation #2020

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions support/windows-server/backup-and-storage/fix-heavy-memory-usage-refs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,8 +63,8 @@ Value Type: **REG_DWORD**

ReFS has a lazy MM unmap logic. So when ReFS cycles the entire namespace to complete an MM unmap, it unmaps at a certain granularity. The amount of virtual address space that is unmapped is determined by the following formula:

RefsNumberOfChunksToTrim *128 MB (for volume of size > 10 TB)
RefsNumberOfChunksToTrim* 64 MB (for volume of size < 10 TB)
* `RefsNumberOfChunksToTrim * 128 MB` (for volume of size > 10 TB)
* `RefsNumberOfChunksToTrim * 64 MB` (for volume of size < 10 TB)

This option works if the VA range that's being unmapped doesn't have any active references (that is, mapped metadata pages).

Expand Down