dsccommunity / dsccommunity/ComputerManagementDsc
xVirtualMemory - Feature Request - Match memory
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 338
- Forks
- 80
- PR merge metrics
- No merged PRs in 30d
Description
It would be great if there was a 5th type of page settings that set the page file to the exact size of the memory installed. For example, if your server had 8GB of RAM. xVirtualMemory would configure the page file (on your specified location) to be 8GB. This would mean if we changed the servers memory to say 16GB, xVirtualMemory would automatically change the paging file to 16GB without having to re-compile the MOF file.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the xVirtualMemory DSC resource and review its existing page-setting options and related tests, if present. Define the new setting so the paging file at the specified location matches installed memory and updates when memory changes, without recompiling the MOF file. Done means the behavior is covered by tests and works alongside the existing settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100