Timeline for On an idle instance, why does setting max memory to 256mb cause %CPU to jump
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 14, 2015 at 17:07 | comment | added | SQLmojoe | Can you monitor paging and context switching counters at the different memory settings? SQL Server needs a minimum amount of memory just to run (as indicated by Andrew) the base engine and 256MB is right on the edge of the threshold. An idle bare bones server instance uses just about 200MB to run system threads. Additional services/features (like AVG) will have incremental consumption. Also, check the error logs to see if there are memory related entries or other stuff causing problems. | |
| Dec 14, 2015 at 5:29 | comment | added | Andrew Loree | Why would you waste your time? Anything less than 1GB is not supported by the vendor (Microsoft). While the fact that they let you set it that low is problematic it self, it doesn't mean you should - msdn.microsoft.com/en-us/library/ms143506(v=sql.110).aspx | |
| Dec 12, 2015 at 13:44 | answer | added | Nicolas Souquet | timeline score: 0 | |
| Dec 11, 2015 at 21:25 | comment | added | Rick | We are aware of our options and probably will end shutting it down. But for now, folks are perplexed (and blaming inefficient mirroring overhead) and looking for an answer. | |
| Dec 11, 2015 at 21:15 | comment | added | Kin Shah | If the instance is not being used, just shut it down. Why waste 256MB when you cannot afford even 1GB. | |
| Dec 11, 2015 at 21:14 | comment | added | Hannah Vernon♦ | Windows Performance Toolkit may allow you to understand why that is happening if you have the luxury of setting up a test system (ie do not use WPT on a production system!) | |
| Dec 11, 2015 at 21:13 | history | edited | Hannah Vernon♦ |
edited tags; edited tags
|
|
| Dec 11, 2015 at 21:05 | review | First posts | |||
| Dec 11, 2015 at 21:27 | |||||
| Dec 11, 2015 at 21:04 | history | asked | Rick | CC BY-SA 3.0 |