linux top load average seems too high

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












1














Following this https://unix.stackexchange.com/a/279354/108702, I ran;



lscpu | grep -E '^Thread|^Core|^Socket|^CPU('
CPU(s): 8
Thread(s) per core: 2
Core(s) per socket: 4
Socket(s): 1


However with top:



top - 01:06:47 up 51 days, 6:24, 2 users, load average: 23.67, 22.50, 22.40
Tasks: 5989 total, 1 running, 5919 sleeping, 0 stopped, 0 zombie
%Cpu(s): 84.6 us, 2.7 sy, 0.0 ni, 12.3 id, 0.4 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem : 32799488 total, 940020 free, 18284088 used, 13575380 buff/cache
KiB Swap: 0 total, 0 free, 0 used. 14034316 avail Mem


What am I missing? I was expecting a load of 2 * 4 * 1 = 8 maximum (at 100% use)?
(Also, is it too high?)










share|improve this question


























    1














    Following this https://unix.stackexchange.com/a/279354/108702, I ran;



    lscpu | grep -E '^Thread|^Core|^Socket|^CPU('
    CPU(s): 8
    Thread(s) per core: 2
    Core(s) per socket: 4
    Socket(s): 1


    However with top:



    top - 01:06:47 up 51 days, 6:24, 2 users, load average: 23.67, 22.50, 22.40
    Tasks: 5989 total, 1 running, 5919 sleeping, 0 stopped, 0 zombie
    %Cpu(s): 84.6 us, 2.7 sy, 0.0 ni, 12.3 id, 0.4 wa, 0.0 hi, 0.0 si, 0.0 st
    KiB Mem : 32799488 total, 940020 free, 18284088 used, 13575380 buff/cache
    KiB Swap: 0 total, 0 free, 0 used. 14034316 avail Mem


    What am I missing? I was expecting a load of 2 * 4 * 1 = 8 maximum (at 100% use)?
    (Also, is it too high?)










    share|improve this question
























      1












      1








      1


      1





      Following this https://unix.stackexchange.com/a/279354/108702, I ran;



      lscpu | grep -E '^Thread|^Core|^Socket|^CPU('
      CPU(s): 8
      Thread(s) per core: 2
      Core(s) per socket: 4
      Socket(s): 1


      However with top:



      top - 01:06:47 up 51 days, 6:24, 2 users, load average: 23.67, 22.50, 22.40
      Tasks: 5989 total, 1 running, 5919 sleeping, 0 stopped, 0 zombie
      %Cpu(s): 84.6 us, 2.7 sy, 0.0 ni, 12.3 id, 0.4 wa, 0.0 hi, 0.0 si, 0.0 st
      KiB Mem : 32799488 total, 940020 free, 18284088 used, 13575380 buff/cache
      KiB Swap: 0 total, 0 free, 0 used. 14034316 avail Mem


      What am I missing? I was expecting a load of 2 * 4 * 1 = 8 maximum (at 100% use)?
      (Also, is it too high?)










      share|improve this question













      Following this https://unix.stackexchange.com/a/279354/108702, I ran;



      lscpu | grep -E '^Thread|^Core|^Socket|^CPU('
      CPU(s): 8
      Thread(s) per core: 2
      Core(s) per socket: 4
      Socket(s): 1


      However with top:



      top - 01:06:47 up 51 days, 6:24, 2 users, load average: 23.67, 22.50, 22.40
      Tasks: 5989 total, 1 running, 5919 sleeping, 0 stopped, 0 zombie
      %Cpu(s): 84.6 us, 2.7 sy, 0.0 ni, 12.3 id, 0.4 wa, 0.0 hi, 0.0 si, 0.0 st
      KiB Mem : 32799488 total, 940020 free, 18284088 used, 13575380 buff/cache
      KiB Swap: 0 total, 0 free, 0 used. 14034316 avail Mem


      What am I missing? I was expecting a load of 2 * 4 * 1 = 8 maximum (at 100% use)?
      (Also, is it too high?)







      linux cpu load-average






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 14 at 0:14









      nha

      1084




      1084




















          2 Answers
          2






          active

          oldest

          votes


















          4














          TL;DR, 23 is probably too high.



          The easiest way to think of load is "number of processes in the queue to use a CPU". If the load exactly matches the CPU count, the number of processes needing CPU exactly matches the available CPU, and you have ideal usage. If the load is higher than the number of CPUs available, then some processes had to wait for CPU to be available, and you're not achieving ideal throughput because you don't have enough resources. If load is lower than CPU count, some CPUs are sitting idle, and you can probably get more throughput from this box.



          It's a useful counter to CPU usage, because it tells you how oversubscribed you are; CPU usage will tell you instantaneous consumption, but if all your cores are running at 100%, that might actually be ideal - what matters here is the load average, it will tell you how big the queue is. As an analogy, it's OK to have a worker at McDonalds serving customers 100% of the time, what matters is how many people are waiting to be served. This is what load average is telling you.



          This is a simplification, of course, the there are technicalities and subtleties galore, but for 95% of us it's a good enough rule to gauge the demand on your system and interpret what load average is tell you.






          share|improve this answer




























            1














            A load average of 1 means that a single cpu or core was 100% busy for the past X minutes (depends on where that 1 is, assume it is in first position so 1 minute)



            So with 4 cores a load average of 4 x x indicates that all of your cores have been 100% busy. Even assuming all of the work being done was hyperthread appropriate, 100% busy would be a LA of 8 x x ...



            This may be of interest - https://www.tecmint.com/understand-linux-load-averages-and-monitor-performance/






            share|improve this answer




















              Your Answer








              StackExchange.ready(function()
              var channelOptions =
              tags: "".split(" "),
              id: "106"
              ;
              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%2funix.stackexchange.com%2fquestions%2f487890%2flinux-top-load-average-seems-too-high%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









              4














              TL;DR, 23 is probably too high.



              The easiest way to think of load is "number of processes in the queue to use a CPU". If the load exactly matches the CPU count, the number of processes needing CPU exactly matches the available CPU, and you have ideal usage. If the load is higher than the number of CPUs available, then some processes had to wait for CPU to be available, and you're not achieving ideal throughput because you don't have enough resources. If load is lower than CPU count, some CPUs are sitting idle, and you can probably get more throughput from this box.



              It's a useful counter to CPU usage, because it tells you how oversubscribed you are; CPU usage will tell you instantaneous consumption, but if all your cores are running at 100%, that might actually be ideal - what matters here is the load average, it will tell you how big the queue is. As an analogy, it's OK to have a worker at McDonalds serving customers 100% of the time, what matters is how many people are waiting to be served. This is what load average is telling you.



              This is a simplification, of course, the there are technicalities and subtleties galore, but for 95% of us it's a good enough rule to gauge the demand on your system and interpret what load average is tell you.






              share|improve this answer

























                4














                TL;DR, 23 is probably too high.



                The easiest way to think of load is "number of processes in the queue to use a CPU". If the load exactly matches the CPU count, the number of processes needing CPU exactly matches the available CPU, and you have ideal usage. If the load is higher than the number of CPUs available, then some processes had to wait for CPU to be available, and you're not achieving ideal throughput because you don't have enough resources. If load is lower than CPU count, some CPUs are sitting idle, and you can probably get more throughput from this box.



                It's a useful counter to CPU usage, because it tells you how oversubscribed you are; CPU usage will tell you instantaneous consumption, but if all your cores are running at 100%, that might actually be ideal - what matters here is the load average, it will tell you how big the queue is. As an analogy, it's OK to have a worker at McDonalds serving customers 100% of the time, what matters is how many people are waiting to be served. This is what load average is telling you.



                This is a simplification, of course, the there are technicalities and subtleties galore, but for 95% of us it's a good enough rule to gauge the demand on your system and interpret what load average is tell you.






                share|improve this answer























                  4












                  4








                  4






                  TL;DR, 23 is probably too high.



                  The easiest way to think of load is "number of processes in the queue to use a CPU". If the load exactly matches the CPU count, the number of processes needing CPU exactly matches the available CPU, and you have ideal usage. If the load is higher than the number of CPUs available, then some processes had to wait for CPU to be available, and you're not achieving ideal throughput because you don't have enough resources. If load is lower than CPU count, some CPUs are sitting idle, and you can probably get more throughput from this box.



                  It's a useful counter to CPU usage, because it tells you how oversubscribed you are; CPU usage will tell you instantaneous consumption, but if all your cores are running at 100%, that might actually be ideal - what matters here is the load average, it will tell you how big the queue is. As an analogy, it's OK to have a worker at McDonalds serving customers 100% of the time, what matters is how many people are waiting to be served. This is what load average is telling you.



                  This is a simplification, of course, the there are technicalities and subtleties galore, but for 95% of us it's a good enough rule to gauge the demand on your system and interpret what load average is tell you.






                  share|improve this answer












                  TL;DR, 23 is probably too high.



                  The easiest way to think of load is "number of processes in the queue to use a CPU". If the load exactly matches the CPU count, the number of processes needing CPU exactly matches the available CPU, and you have ideal usage. If the load is higher than the number of CPUs available, then some processes had to wait for CPU to be available, and you're not achieving ideal throughput because you don't have enough resources. If load is lower than CPU count, some CPUs are sitting idle, and you can probably get more throughput from this box.



                  It's a useful counter to CPU usage, because it tells you how oversubscribed you are; CPU usage will tell you instantaneous consumption, but if all your cores are running at 100%, that might actually be ideal - what matters here is the load average, it will tell you how big the queue is. As an analogy, it's OK to have a worker at McDonalds serving customers 100% of the time, what matters is how many people are waiting to be served. This is what load average is telling you.



                  This is a simplification, of course, the there are technicalities and subtleties galore, but for 95% of us it's a good enough rule to gauge the demand on your system and interpret what load average is tell you.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Dec 14 at 3:41









                  GarethHumphriesAcc

                  812




                  812























                      1














                      A load average of 1 means that a single cpu or core was 100% busy for the past X minutes (depends on where that 1 is, assume it is in first position so 1 minute)



                      So with 4 cores a load average of 4 x x indicates that all of your cores have been 100% busy. Even assuming all of the work being done was hyperthread appropriate, 100% busy would be a LA of 8 x x ...



                      This may be of interest - https://www.tecmint.com/understand-linux-load-averages-and-monitor-performance/






                      share|improve this answer

























                        1














                        A load average of 1 means that a single cpu or core was 100% busy for the past X minutes (depends on where that 1 is, assume it is in first position so 1 minute)



                        So with 4 cores a load average of 4 x x indicates that all of your cores have been 100% busy. Even assuming all of the work being done was hyperthread appropriate, 100% busy would be a LA of 8 x x ...



                        This may be of interest - https://www.tecmint.com/understand-linux-load-averages-and-monitor-performance/






                        share|improve this answer























                          1












                          1








                          1






                          A load average of 1 means that a single cpu or core was 100% busy for the past X minutes (depends on where that 1 is, assume it is in first position so 1 minute)



                          So with 4 cores a load average of 4 x x indicates that all of your cores have been 100% busy. Even assuming all of the work being done was hyperthread appropriate, 100% busy would be a LA of 8 x x ...



                          This may be of interest - https://www.tecmint.com/understand-linux-load-averages-and-monitor-performance/






                          share|improve this answer












                          A load average of 1 means that a single cpu or core was 100% busy for the past X minutes (depends on where that 1 is, assume it is in first position so 1 minute)



                          So with 4 cores a load average of 4 x x indicates that all of your cores have been 100% busy. Even assuming all of the work being done was hyperthread appropriate, 100% busy would be a LA of 8 x x ...



                          This may be of interest - https://www.tecmint.com/understand-linux-load-averages-and-monitor-performance/







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Dec 14 at 0:29









                          ivanivan

                          3,4971414




                          3,4971414



























                              draft saved

                              draft discarded
















































                              Thanks for contributing an answer to Unix & Linux 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.





                              Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                              Please pay close attention to the following guidance:


                              • 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%2funix.stackexchange.com%2fquestions%2f487890%2flinux-top-load-average-seems-too-high%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

                              How to check contact read email or not when send email to Individual?

                              Bahrain

                              Postfix configuration issue with fips on centos 7; mailgun relay