1 2 Previous Next 18 Replies Latest reply on May 15, 2013 7:02 PM by Bill Robinson

    Red Hat patch catalog update performance

      I am in need of adding subchannels to my RHEL5 patch catalog and need to create a new RHEL 6 patch catalog.

       

      I have been experimenting with changing our existing online catalog to an offline catalog but I am encountering performance problems related to the time required to update the new offline catalog.

       

      The existing online catalog has the base channel for RHEL5 32 and 64 bit architectures.  This catalog usually takes about 45 minutes to update.  I created an offline catalog with RHEL5 32 and 64 bit (include a few subchannels) and RHEL6 64 bit (with some sub channels).  After I offline downloader completes (which takes about 1.5 hours) the patch catalog update takes and additional 5-6 hours to update.  This is an impact on our patching operations and I need to find a method that drastically reduces this time.

       

      Can anyone suggest any performance tweaks to improve the patch catalog update for a Red Hat patch catalog?

       

      Clip from log catalog update log:

       

      Apr 4, 2013 9:46:11 AM Processing erratas for os-architecure - RHES5x86_64

      Apr 4, 2013 1:13:47 PM Processing erratas for os-architecure - RHES6x86_64

      Apr 4, 2013 2:36:29 PM Processing erratas for os-architecure - RHES5x86

      Apr 4, 2013 2:36:33 PM Catalog update progress is 8% completed. Updating metadata : 1/5 completed.

      Apr 4, 2013 2:36:33 PM Processing all rpms meta data for the os-Architecture - RHES5x86_64

      Apr 4, 2013 2:45:44 PM Processing all rpms meta data for the os-Architecture - RHES6x86_64

      Apr 4, 2013 3:10:27 PM Processing all rpms meta data for the os-Architecture - RHES5x86

      Apr 4, 2013 3:14:09 PM Catalog update progress is 16% completed. Updating metadata : 2/5 completed.

        1 2 Previous Next