Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!

pigz / pkgacct high cpu

Discussion in 'Data Protection' started by theallan, Jul 13, 2017.

Tags:
  1. theallan

    theallan Active Member

    Joined:
    Nov 17, 2005
    Messages:
    36
    Likes Received:
    2
    Trophy Points:
    158
    I'm seeing a very high CPU from pigz when the backup process is running:

    PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
    22280 root 39 19 11808 1268 560 R 94.4 0.0 346:57.55 pigz
    15894 root 39 19 507m 413m 4352 S 17.9 1.3 50:12.94 pkgacct - allan

    Its a large account, around 50Gb, so I'm not suprised that it will take a while to zip up, although the amount of time in the process is very concerning 50 hours for pkgacct and 348 hours for pigz...

    What is concerning me most is the impact this is having on the web server. The load average is:

    load average: 3.44, 2.39, 2.26

    but even when its been down around 1, the load time has been exceptionally slow.

    What can I do to improve this - both the zip time and more importantly keeping the server performant during the backup?

    Thanks,
    Allan
     
    #1 theallan, Jul 13, 2017
  2. cPanelMichael

    cPanelMichael Technical Support Community Manager Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    47,555
    Likes Received:
    2,182
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Twitter:
    Hello Allan,

    The following options are available under the "Compression" tab in "WHM >> Tweak Settings":

    gzip compression level - The level of compression to use (0 is faster but less compression, 9 is slower but provides maximum compression)

    Number of pigz processes - The number of independent pigz processes to use when performing gzip compression. For quickest compression, specify the same number of cores available on your server.

    Number of kilobyte chunks per compression work unit -
    The size (in 1024 byte chunks) of compression work units to be distributed to each pigz process. Default is 4096. Systems with larger L2/L3 caches may benefit from higher values.

    Could you try modifying the values for these options for faster compression times (with less compression) to see if that helps during the next backup generation?

    Thank you.
     
    #2 cPanelMichael, Jul 13, 2017
(You must log in or sign up to post here.)
Loading...
Similar Threads - pigz pkgacct high
  1. ottdev

    baseline/optimal pigz block size (chunks per compression unit)

    ottdev, Mar 27, 2018, in forum: Workarounds and Optimization
    Replies:
    1
    Views:
    754
    cPanelMichael
    Mar 27, 2018
  2. djblamire

    SOLVED Deprecation and Removal of Legacy Backups - Pkgacct script ?

    djblamire, Oct 17, 2018, in forum: Data Protection
    Replies:
    5
    Views:
    312
    cPanelLauren
    Oct 17, 2018
  3. Josh Strike

    pkgacct mysql error since 70.0.42 update

    Josh Strike, May 17, 2018, in forum: Data Protection
    Replies:
    3
    Views:
    493
    cPanelMichael
    May 21, 2018
  4. Sametto Chan

    The process pkgacct stalled while it ran for user

    Sametto Chan, Dec 11, 2017, in forum: General Discussion
    Replies:
    5
    Views:
    1,672
    cPanelMichael
    Dec 12, 2017
  5. Jason Kohut

    WHM API 1 Backup Destination for start_background_pkgacct

    Jason Kohut, Sep 14, 2017, in forum: cPanel Developers
    Replies:
    1
    Views:
    586
    cPanelMichael
    Sep 18, 2017

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...
    Dismiss Notice