dsccommunity / dsccommunity/SqlServerDsc
SqlMemory: We should look over the dynamic memory allocation algorithm
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 385
- Forks
- 224
- PR merge metrics
- No merged PRs in 30d
Description
This was broken out from an unrelated discussion in a PR. Thanks to @Fiander for pointing out this.
"I really don't like the autotune of SqlMemory. It is just plain wrong.
It should include a test for full text, and substract memory for full text .
https://docs.microsoft.com/en-us/sql/relational-databases/search/improve-the-performance-of-full-text-indexes?view=sql-server-ver15
it should also not change memory settings if the change is less then 1%.
Each time MaxMemory gets changed, the procedure cache is invalidated https://jasonbrimhall.info/2015/01/05/effects-of-max-mem-on-plan-cache/"
Originally posted by @Fiander in https://github.com/dsccommunity/SqlServerDsc/issues/1633#issuecomment-732419809
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
No files or tests are identified in the issue. Start by locating the SqlMemory autotune algorithm and review how it accounts for full-text memory and changes MaxMemory. Done should include full-text memory handling and avoiding memory-setting changes below the stated 1% threshold, with the plan-cache impact addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, sql
- Domain
- databases, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100