Set System Load Value for Backups

osirion

• February 27, 2016 02:37

Hi Guys, So when I get a report from my daily backups, I often see: "System load is currently 3.76; waiting for it to go down to 3.50 to continue " cpuwatch: System load is currently 3.26, which is below the threshold of 3.50. Continuing "" So, how do I change the 3.5 value down to something lower so it only runs when the server isnt busy at all (eg, 2.0)? This is a Intel(R) Xeon(R) CPU E3-1220L v2 (2 cores, 4 threads) with 4GB of RAM.

• 

  24x7server

  • February 27, 2016 13:21

  Hello :), You can change your Critical load threshold in your tweak setting. Tweak Settings - Status - 11.44 Documentation - cPanel Documentation

  0
• 

  syslint

  • February 28, 2016 03:43

  Hi Guys, So, how do I change the 3.5 value down to something lower so it only runs when the server isnt busy at all (eg, 2.0)? This is a Intel(R) Xeon(R) CPU E3-1220L v2 (2 cores, 4 threads) with 4GB of RAM.

  
  Do you know exactly when the serve is not busy ? ,if so change the backup cron time. You whm already have the load settings threshold as showing it above.

  0
• 

  osirion

  • February 28, 2016 05:42

  I've got Munin running, so will better optimise the start time there Syslint - thanks :) Thanks 24x7Server - will go change it now!

  0
• 

  osirion

  • February 28, 2016 05:46

  Hello :), You can change your Critical load threshold in your tweak setting.

  0
• 

  osirion

  • February 28, 2016 05:56

  I did manage to find something else in Tweak Settings which will help with the end goal though! For those looking for a similar solution, check out the options: I/O priority level at which nightly backups are run I/O priority level at which cPanel-generated backups are run

  0
• 

  cPanelMichael

  • February 29, 2016 15:27

  Hello :) You can also change the "Extra CPUs for server load" value under the "Stats and Logs" tab in "WHM >> Tweak Settings". Per it's description: This setting allows you to specify a value to add to the number of physical CPUs in your server. The sum of these two numbers becomes the value at which the cpuwatch, cpanellogd, backups, and CPU statistics daemons consider the system to be in a critical load state. This setting defaults to 0.
  Thank you.

  0

Please sign in to leave a comment.