3 Replies Latest reply: May 22, 2013 11:58 AM by rmetzger RSS

    Slow Scan times that can't be explained

    Dvanmeter

      I am trying to figure out the cause of a problem with some systems taking a long time to scan that really shouldnt.  This has occurred randonly on server and workstations.  when monitoring an on-demand scan on the device the memory scan alone took 15-20 minutes.  I am used to memory scans only taking less that one minute of the scan time.  a device running window 2003 with only a 30gb drive and 4gb free space is taking over 9 hours to complete.  The scan has archives turned off and that only reduced the scanning time by a bit.  removing McAfee doesnt help or applying all the latest hotfixes.  Just wondering if anyone has ever seen this behavior or have any tips.  These devices are not running anything unusual,  not stressed, or have high IO read or writes.

        • 1. Re: Slow Scan times that can't be explained
          rmetzger

          During this 'slow scan' how is the system running otherwise? Is it running slow everywhere, or just the scan? What is the CPU running at during this slowness?

           

          Since this is happening 'randomly,' it might be helpful to pre-install McAfee's Profiler on some suspect system, then initiate it when you see it running slow. Maybe that will highlight something useful.

           

          Ron Metzger

          • 2. Re: Slow Scan times that can't be explained
            Dvanmeter

            The systems have no performance issues other than when the memory scan is initiated.  It also is the source of slowness when dats are updated with the scan processes setting turned on.  I have turned on McAfee profiler and found no processes doing any large number of writes/reads or cpu usage.

            • 3. Re: Slow Scan times that can't be explained
              rmetzger

              Well with limited info, I can only make an educated Guess. Try increasing the process priority to the next higher level. This will increase the amount of CPU McShield has available to improve the ODS. It could be that ODS has so little processor available that it is giving away all chance of completing in any reasonable time. If other equal or higher priority threads are grabbing the CPU and McShield is giving way, the ODS may not ever get enough CPU cycles to actually run.

               

              From the VirusScan Console,

              on EACH ODS defined -> Properties -> Performance tab -> increase System utilization.

              Don't forget to do this for the default ODS ->

              Task -> Properties -> Performance tab -> increase System utilization.

               

              Dvanmeter wrote:

               

              It also is the source of slowness when dats are updated with the scan processes setting turned on.

              Scan processes setting turned on? Do you mean 'Processes on Enable?' If so, turn this OFF. This setting is redundant and is not really recommended, unless Security is the only priority and Performance is irrelevant in your environment.

               

              From the VirusScan Console,

              On-Access Scanner -> Properties -> General tab -> Scan section: Disable 'Processes on enable'

               

              Let us know if either of these helps.

               

              Ron Metzger