Limit max CPU usage SQL SERVER with WSRM Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern)SQL Server performing slowSQL Server Maximum and Minimum memory configurationLimit CPU usage without Resource GovernorMonitoring sql serverHow to troubleshoot how resource governed query is being throttled in SQL 2012?Resource Governor on 2014 - CPU Not Being ThrottledSql Server 2016 Counter Reporting ZeroSQL Server not using all NUMA memory with 20 core limit and affinity maskWhy low cpu usage on sql server developer edition 2014SQL Server 2016 with high tempdb usage and low RAM usage

Why is it faster to reheat something than it is to cook it?

How to write the following sign?

How to react to hostile behavior from a senior developer?

What is the appropriate index architecture when forced to implement IsDeleted (soft deletes)?

Converted a Scalar function to a TVF function for parallel execution-Still running in Serial mode

Denied boarding although I have proper visa and documentation. To whom should I make a complaint?

Take 2! Is this homebrew Lady of Pain warlock patron balanced?

Is CEO the "profession" with the most psychopaths?

How to write this math term? with cases it isn't working

Selecting user stories during sprint planning

Why does it sometimes sound good to play a grace note as a lead in to a note in a melody?

Why does the remaining Rebel fleet at the end of Rogue One seem dramatically larger than the one in A New Hope?

Is it possible for SQL statements to execute concurrently within a single session in SQL Server?

Performance gap between vector<bool> and array

What does it mean that physics no longer uses mechanical models to describe phenomena?

Morning, Afternoon, Night Kanji

Dating a Former Employee

Disembodied hand growing fangs

Central Vacuuming: Is it worth it, and how does it compare to normal vacuuming?

How could we fake a moon landing now?

What is a fractional matching?

How can I reduce the gap between left and right of cdot with a macro?

Is it a good idea to use CNN to classify 1D signal?

Did Deadpool rescue all of the X-Force?



Limit max CPU usage SQL SERVER with WSRM



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern)SQL Server performing slowSQL Server Maximum and Minimum memory configurationLimit CPU usage without Resource GovernorMonitoring sql serverHow to troubleshoot how resource governed query is being throttled in SQL 2012?Resource Governor on 2014 - CPU Not Being ThrottledSql Server 2016 Counter Reporting ZeroSQL Server not using all NUMA memory with 20 core limit and affinity maskWhy low cpu usage on sql server developer edition 2014SQL Server 2016 with high tempdb usage and low RAM usage



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








10















I have a physical server running one instance of SQL Server.



I notice that quite often this server is running at 100% CPU usage.



My IT team is not happy about this, and suggested we reserve 2 of the 32 cores for the OS.



This works great, now max usage peak just under 90%. Additionally, slow data retrieval from various users is no longer reported.



Is there any reason NOT to use WSRM (Windows System Resource Manager) in this way - instead of SQL Resource Governor?










share|improve this question
























  • Do you really want to use all the CPU? Saving a couple of cores for the OS seems prudent doesn't it? On my workstation, if I use all cores for some number crunching my machine grinds to a halt. I always keep a few cores free. Would this not be good practice on a machine dedicated to SQL Server too?

    – ManInMoon
    Mar 20 at 12:22











  • What kind of load is running on this server? What type of process is using 100% of CPU? Is this OLTP or analytics or graph or ?

    – Max Vernon
    Mar 20 at 12:40











  • @Forrest When you say tuning - do you mean the SQL Server itself - or the queries/table structure? If you mean SQL Server, please give me a link to what to look at. If queiries/tables, then I optmise them when I can, but some users are less design conscious!

    – ManInMoon
    Mar 20 at 12:45

















10















I have a physical server running one instance of SQL Server.



I notice that quite often this server is running at 100% CPU usage.



My IT team is not happy about this, and suggested we reserve 2 of the 32 cores for the OS.



This works great, now max usage peak just under 90%. Additionally, slow data retrieval from various users is no longer reported.



Is there any reason NOT to use WSRM (Windows System Resource Manager) in this way - instead of SQL Resource Governor?










share|improve this question
























  • Do you really want to use all the CPU? Saving a couple of cores for the OS seems prudent doesn't it? On my workstation, if I use all cores for some number crunching my machine grinds to a halt. I always keep a few cores free. Would this not be good practice on a machine dedicated to SQL Server too?

    – ManInMoon
    Mar 20 at 12:22











  • What kind of load is running on this server? What type of process is using 100% of CPU? Is this OLTP or analytics or graph or ?

    – Max Vernon
    Mar 20 at 12:40











  • @Forrest When you say tuning - do you mean the SQL Server itself - or the queries/table structure? If you mean SQL Server, please give me a link to what to look at. If queiries/tables, then I optmise them when I can, but some users are less design conscious!

    – ManInMoon
    Mar 20 at 12:45













10












10








10








I have a physical server running one instance of SQL Server.



I notice that quite often this server is running at 100% CPU usage.



My IT team is not happy about this, and suggested we reserve 2 of the 32 cores for the OS.



This works great, now max usage peak just under 90%. Additionally, slow data retrieval from various users is no longer reported.



Is there any reason NOT to use WSRM (Windows System Resource Manager) in this way - instead of SQL Resource Governor?










share|improve this question
















I have a physical server running one instance of SQL Server.



I notice that quite often this server is running at 100% CPU usage.



My IT team is not happy about this, and suggested we reserve 2 of the 32 cores for the OS.



This works great, now max usage peak just under 90%. Additionally, slow data retrieval from various users is no longer reported.



Is there any reason NOT to use WSRM (Windows System Resource Manager) in this way - instead of SQL Resource Governor?







sql-server configuration windows resource-governor






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 21 at 4:53









Paul White

54.3k14288461




54.3k14288461










asked Mar 20 at 12:11









ManInMoonManInMoon

1967




1967












  • Do you really want to use all the CPU? Saving a couple of cores for the OS seems prudent doesn't it? On my workstation, if I use all cores for some number crunching my machine grinds to a halt. I always keep a few cores free. Would this not be good practice on a machine dedicated to SQL Server too?

    – ManInMoon
    Mar 20 at 12:22











  • What kind of load is running on this server? What type of process is using 100% of CPU? Is this OLTP or analytics or graph or ?

    – Max Vernon
    Mar 20 at 12:40











  • @Forrest When you say tuning - do you mean the SQL Server itself - or the queries/table structure? If you mean SQL Server, please give me a link to what to look at. If queiries/tables, then I optmise them when I can, but some users are less design conscious!

    – ManInMoon
    Mar 20 at 12:45

















  • Do you really want to use all the CPU? Saving a couple of cores for the OS seems prudent doesn't it? On my workstation, if I use all cores for some number crunching my machine grinds to a halt. I always keep a few cores free. Would this not be good practice on a machine dedicated to SQL Server too?

    – ManInMoon
    Mar 20 at 12:22











  • What kind of load is running on this server? What type of process is using 100% of CPU? Is this OLTP or analytics or graph or ?

    – Max Vernon
    Mar 20 at 12:40











  • @Forrest When you say tuning - do you mean the SQL Server itself - or the queries/table structure? If you mean SQL Server, please give me a link to what to look at. If queiries/tables, then I optmise them when I can, but some users are less design conscious!

    – ManInMoon
    Mar 20 at 12:45
















Do you really want to use all the CPU? Saving a couple of cores for the OS seems prudent doesn't it? On my workstation, if I use all cores for some number crunching my machine grinds to a halt. I always keep a few cores free. Would this not be good practice on a machine dedicated to SQL Server too?

– ManInMoon
Mar 20 at 12:22





Do you really want to use all the CPU? Saving a couple of cores for the OS seems prudent doesn't it? On my workstation, if I use all cores for some number crunching my machine grinds to a halt. I always keep a few cores free. Would this not be good practice on a machine dedicated to SQL Server too?

– ManInMoon
Mar 20 at 12:22













What kind of load is running on this server? What type of process is using 100% of CPU? Is this OLTP or analytics or graph or ?

– Max Vernon
Mar 20 at 12:40





What kind of load is running on this server? What type of process is using 100% of CPU? Is this OLTP or analytics or graph or ?

– Max Vernon
Mar 20 at 12:40













@Forrest When you say tuning - do you mean the SQL Server itself - or the queries/table structure? If you mean SQL Server, please give me a link to what to look at. If queiries/tables, then I optmise them when I can, but some users are less design conscious!

– ManInMoon
Mar 20 at 12:45





@Forrest When you say tuning - do you mean the SQL Server itself - or the queries/table structure? If you mean SQL Server, please give me a link to what to look at. If queiries/tables, then I optmise them when I can, but some users are less design conscious!

– ManInMoon
Mar 20 at 12:45










2 Answers
2






active

oldest

votes


















14














Is there any reason NOT to use the approach you've defined? Absolutely.



Imagine you had bought a car - a car that when you hit 50MPH the engine starts to overheat. Would your reaction to this situation be to artificially limit the car to 49MPH, or to find out what the fault is with the engine?



Why should you limit your car to 49MPH? The manufacturer stated that it could drive as fast as 80MPH - you like to drive your car fast so you want to get it to this speed - if it wasn't for that damn overheating issue.



The car you bought was also really, really expensive. Each engine cylinder needs to be utilised to the max so you aren't wasting that money!



By artificially limiting SQL Servers access to the CPU, you are missing out on performance. You may have temporarily resolved the performance issues by ensuring the CPU is available for the OS to use, but you haven't answered the real question - WHY is SQL Server using 100% of the CPU?



My advice is as follows:



Find out what the real issue is, and fix it. Don't cover the issue up with what is effectively a kludge. The issue WILL reappear and smack you in the face down the line when the workload of the server naturally increases with growth.



As a temporary fix, resource governor can be used to lower the CPU used, UNTIL YOU FIND THE REAL PROBLEM.






share|improve this answer
































    11














    Erik Darling mentioned the biggest practical reason for not using WSRM in a comment on your question:




    ...there's no reciprocal limiting of CPU use in other processes. SQL Server may not use those two cores, but other things may use the other 30 SQL Server is using. It's a crapshoot, really.




    If this is working for you, then stick with it - we're all busy, and you can only spend so much time on any given problem. The ideal solution would be to fix the underlying queries / issues that are driving CPU to the point of user-noticeable problems (which George covers in his excellent answer).



    Erik goes on to say




    Plus, you're paying SQL Server licensing for them.




    From a business standpoint, this is probably the worst part of the WSRM deal - you're paying per-core licensing for 2 cores that are explicitly not being used. At the time of this writing, that's $3k or $14k left on the table (depending on Standard vs Enterprise).






    share|improve this answer























      Your Answer








      StackExchange.ready(function()
      var channelOptions =
      tags: "".split(" "),
      id: "182"
      ;
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function()
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled)
      StackExchange.using("snippets", function()
      createEditor();
      );

      else
      createEditor();

      );

      function createEditor()
      StackExchange.prepareEditor(
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader:
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      ,
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      );



      );













      draft saved

      draft discarded


















      StackExchange.ready(
      function ()
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f232605%2flimit-max-cpu-usage-sql-server-with-wsrm%23new-answer', 'question_page');

      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      14














      Is there any reason NOT to use the approach you've defined? Absolutely.



      Imagine you had bought a car - a car that when you hit 50MPH the engine starts to overheat. Would your reaction to this situation be to artificially limit the car to 49MPH, or to find out what the fault is with the engine?



      Why should you limit your car to 49MPH? The manufacturer stated that it could drive as fast as 80MPH - you like to drive your car fast so you want to get it to this speed - if it wasn't for that damn overheating issue.



      The car you bought was also really, really expensive. Each engine cylinder needs to be utilised to the max so you aren't wasting that money!



      By artificially limiting SQL Servers access to the CPU, you are missing out on performance. You may have temporarily resolved the performance issues by ensuring the CPU is available for the OS to use, but you haven't answered the real question - WHY is SQL Server using 100% of the CPU?



      My advice is as follows:



      Find out what the real issue is, and fix it. Don't cover the issue up with what is effectively a kludge. The issue WILL reappear and smack you in the face down the line when the workload of the server naturally increases with growth.



      As a temporary fix, resource governor can be used to lower the CPU used, UNTIL YOU FIND THE REAL PROBLEM.






      share|improve this answer





























        14














        Is there any reason NOT to use the approach you've defined? Absolutely.



        Imagine you had bought a car - a car that when you hit 50MPH the engine starts to overheat. Would your reaction to this situation be to artificially limit the car to 49MPH, or to find out what the fault is with the engine?



        Why should you limit your car to 49MPH? The manufacturer stated that it could drive as fast as 80MPH - you like to drive your car fast so you want to get it to this speed - if it wasn't for that damn overheating issue.



        The car you bought was also really, really expensive. Each engine cylinder needs to be utilised to the max so you aren't wasting that money!



        By artificially limiting SQL Servers access to the CPU, you are missing out on performance. You may have temporarily resolved the performance issues by ensuring the CPU is available for the OS to use, but you haven't answered the real question - WHY is SQL Server using 100% of the CPU?



        My advice is as follows:



        Find out what the real issue is, and fix it. Don't cover the issue up with what is effectively a kludge. The issue WILL reappear and smack you in the face down the line when the workload of the server naturally increases with growth.



        As a temporary fix, resource governor can be used to lower the CPU used, UNTIL YOU FIND THE REAL PROBLEM.






        share|improve this answer



























          14












          14








          14







          Is there any reason NOT to use the approach you've defined? Absolutely.



          Imagine you had bought a car - a car that when you hit 50MPH the engine starts to overheat. Would your reaction to this situation be to artificially limit the car to 49MPH, or to find out what the fault is with the engine?



          Why should you limit your car to 49MPH? The manufacturer stated that it could drive as fast as 80MPH - you like to drive your car fast so you want to get it to this speed - if it wasn't for that damn overheating issue.



          The car you bought was also really, really expensive. Each engine cylinder needs to be utilised to the max so you aren't wasting that money!



          By artificially limiting SQL Servers access to the CPU, you are missing out on performance. You may have temporarily resolved the performance issues by ensuring the CPU is available for the OS to use, but you haven't answered the real question - WHY is SQL Server using 100% of the CPU?



          My advice is as follows:



          Find out what the real issue is, and fix it. Don't cover the issue up with what is effectively a kludge. The issue WILL reappear and smack you in the face down the line when the workload of the server naturally increases with growth.



          As a temporary fix, resource governor can be used to lower the CPU used, UNTIL YOU FIND THE REAL PROBLEM.






          share|improve this answer















          Is there any reason NOT to use the approach you've defined? Absolutely.



          Imagine you had bought a car - a car that when you hit 50MPH the engine starts to overheat. Would your reaction to this situation be to artificially limit the car to 49MPH, or to find out what the fault is with the engine?



          Why should you limit your car to 49MPH? The manufacturer stated that it could drive as fast as 80MPH - you like to drive your car fast so you want to get it to this speed - if it wasn't for that damn overheating issue.



          The car you bought was also really, really expensive. Each engine cylinder needs to be utilised to the max so you aren't wasting that money!



          By artificially limiting SQL Servers access to the CPU, you are missing out on performance. You may have temporarily resolved the performance issues by ensuring the CPU is available for the OS to use, but you haven't answered the real question - WHY is SQL Server using 100% of the CPU?



          My advice is as follows:



          Find out what the real issue is, and fix it. Don't cover the issue up with what is effectively a kludge. The issue WILL reappear and smack you in the face down the line when the workload of the server naturally increases with growth.



          As a temporary fix, resource governor can be used to lower the CPU used, UNTIL YOU FIND THE REAL PROBLEM.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Mar 20 at 13:18

























          answered Mar 20 at 13:11









          George.PalaciosGeorge.Palacios

          2,726826




          2,726826























              11














              Erik Darling mentioned the biggest practical reason for not using WSRM in a comment on your question:




              ...there's no reciprocal limiting of CPU use in other processes. SQL Server may not use those two cores, but other things may use the other 30 SQL Server is using. It's a crapshoot, really.




              If this is working for you, then stick with it - we're all busy, and you can only spend so much time on any given problem. The ideal solution would be to fix the underlying queries / issues that are driving CPU to the point of user-noticeable problems (which George covers in his excellent answer).



              Erik goes on to say




              Plus, you're paying SQL Server licensing for them.




              From a business standpoint, this is probably the worst part of the WSRM deal - you're paying per-core licensing for 2 cores that are explicitly not being used. At the time of this writing, that's $3k or $14k left on the table (depending on Standard vs Enterprise).






              share|improve this answer



























                11














                Erik Darling mentioned the biggest practical reason for not using WSRM in a comment on your question:




                ...there's no reciprocal limiting of CPU use in other processes. SQL Server may not use those two cores, but other things may use the other 30 SQL Server is using. It's a crapshoot, really.




                If this is working for you, then stick with it - we're all busy, and you can only spend so much time on any given problem. The ideal solution would be to fix the underlying queries / issues that are driving CPU to the point of user-noticeable problems (which George covers in his excellent answer).



                Erik goes on to say




                Plus, you're paying SQL Server licensing for them.




                From a business standpoint, this is probably the worst part of the WSRM deal - you're paying per-core licensing for 2 cores that are explicitly not being used. At the time of this writing, that's $3k or $14k left on the table (depending on Standard vs Enterprise).






                share|improve this answer

























                  11












                  11








                  11







                  Erik Darling mentioned the biggest practical reason for not using WSRM in a comment on your question:




                  ...there's no reciprocal limiting of CPU use in other processes. SQL Server may not use those two cores, but other things may use the other 30 SQL Server is using. It's a crapshoot, really.




                  If this is working for you, then stick with it - we're all busy, and you can only spend so much time on any given problem. The ideal solution would be to fix the underlying queries / issues that are driving CPU to the point of user-noticeable problems (which George covers in his excellent answer).



                  Erik goes on to say




                  Plus, you're paying SQL Server licensing for them.




                  From a business standpoint, this is probably the worst part of the WSRM deal - you're paying per-core licensing for 2 cores that are explicitly not being used. At the time of this writing, that's $3k or $14k left on the table (depending on Standard vs Enterprise).






                  share|improve this answer













                  Erik Darling mentioned the biggest practical reason for not using WSRM in a comment on your question:




                  ...there's no reciprocal limiting of CPU use in other processes. SQL Server may not use those two cores, but other things may use the other 30 SQL Server is using. It's a crapshoot, really.




                  If this is working for you, then stick with it - we're all busy, and you can only spend so much time on any given problem. The ideal solution would be to fix the underlying queries / issues that are driving CPU to the point of user-noticeable problems (which George covers in his excellent answer).



                  Erik goes on to say




                  Plus, you're paying SQL Server licensing for them.




                  From a business standpoint, this is probably the worst part of the WSRM deal - you're paying per-core licensing for 2 cores that are explicitly not being used. At the time of this writing, that's $3k or $14k left on the table (depending on Standard vs Enterprise).







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Mar 20 at 14:05









                  Josh DarnellJosh Darnell

                  8,31922243




                  8,31922243



























                      draft saved

                      draft discarded
















































                      Thanks for contributing an answer to Database Administrators Stack Exchange!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid


                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.

                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function ()
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f232605%2flimit-max-cpu-usage-sql-server-with-wsrm%23new-answer', 'question_page');

                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      Identifying “long and narrow” polygons in with PostGISlength and width of polygonWhy postgis st_overlaps reports Qgis' “avoid intersections” generated polygon as overlapping with others?Adjusting polygons to boundary and filling holesDrawing polygons with fixed area?How to remove spikes in Polygons with PostGISDeleting sliver polygons after difference operation in QGIS?Snapping boundaries in PostGISSplit polygon into parts adding attributes based on underlying polygon in QGISSplitting overlap between polygons and assign to nearest polygon using PostGIS?Expanding polygons and clipping at midpoint?Removing Intersection of Buffers in Same Layers

                      Masuk log Menu navigasi

                      อาณาจักร (ชีววิทยา) ดูเพิ่ม อ้างอิง รายการเลือกการนำทาง10.1086/39456810.5962/bhl.title.447410.1126/science.163.3863.150576276010.1007/BF01796092408502"Phylogenetic structure of the prokaryotic domain: the primary kingdoms"10.1073/pnas.74.11.5088432104270744"Towards a natural system of organisms: proposal for the domains Archaea, Bacteria, and Eucarya"1990PNAS...87.4576W10.1073/pnas.87.12.4576541592112744PubMedJump the queueexpand by handPubMedJump the queueexpand by handPubMedJump the queueexpand by hand"A revised six-kingdom system of life"10.1111/j.1469-185X.1998.tb00030.x9809012"Only six kingdoms of life"10.1098/rspb.2004.2705169172415306349"Kingdoms Protozoa and Chromista and the eozoan root of the eukaryotic tree"10.1098/rsbl.2009.0948288006020031978เพิ่มข้อมูล