2 Replies Latest reply on Jun 7, 2010 8:54 AM by Makke

    Huge performance impact Custom job processor

    Apprentice

      Hi,

       

      We've implemented a new core server based on Windows Server 2008 64-bit and LANDesk Management Suite 9.0.

       

      The core server is a virtual machine with 4 dedicated CPU's.'

       

      We've experienced a huge performance impact on the core server a few times this week. Alle CPU's are working on 100%. This shouldn't be a problem. Unfortunately, remote control isn't possible when this occurs. Our helpdesk uses remote control to control clients and get asked for credentials when they try to. We think this is due to a problem on the core server in resolving group membership in Active Directory for the helpdesk users. When the performance hit on the CPU's is over, remote control is possible again.

       

      We've tried to analyze what is going on on the core. As far as we can see, the Custom Job Processor (Custjob.exe) and some ISS Application Pool Processes are the cause for this performance impact. We need to figure out how to solve this issue.

       

      What does the Custom Job Processor do? How can we find out what it is that this process is doing at the time of the performance impact?

       

      Thanks in advance.

       

      Mark

        • 1. Re: Huge performance impact Custom job processor
          phoffmann SupportEmployee

          CUSTJOB is responsible for anything to do with OSD (notice, specifically OSD - *NOT* provisioning, that goes through IIS) as well as anything that is a "Managed Script".

           

          CUSTJOB generates logs for the relevant jobs its running in the LOG-directory, though it'll be more helpful to figure out first of all how many instances of CUSTJOB are running when you're got 100% usage (I would suspect QUITE a lot, since CUSTJOB isn't that heavy normally).

           

          IIS can be VERY greedy for both CPU and/or memory - it depends on what you're doing with/through it.

           

          Commonly, the #1 "performance eater" as it were is processing vulscans. For analysing IIS log files (in terms of www-site hits, etc.) I have found the following graphical tool very handy (it's the only graphical representation of an IIS log I know of):

          - http://indihiang.codeplex.com/

           

          Updated Documentation for this:
          - http://wiki.indihiang.com/

           

          If IIS is "very busy" it could actually be waiting for the DB - so you may want to work your way through the performance and tuning paper here (it includes performance counters you should use/track and what their values should be):

          - http://community.landesk.com/support/docs/DOC-2356

           

          Hope this helps you along a little bit?

           

          - Paul Hoffmann

          LANDesk EMEA Technical Lead.

          1 of 1 people found this helpful
          • 2. Re: Huge performance impact Custom job processor
            Apprentice

            Hi Paul,

             

            It was helpfull as we weren't running any OSD related tasks and still Custjob.exe was going rampant on our system.

             

            We've killed the proces and rebooted the core server. The proces isn't causing continual problems any more.

             

            Thank you for your help!

             

            Mark