CPU usage

Discussion in 'Other ESET Home Products Beta' started by mbdrake, Jan 29, 2010.

Thread Status:
Not open for further replies.
  1. mbdrake

    mbdrake Registered Member

    Joined:
    Jan 29, 2010
    Posts:
    4
    Hello,

    Have been an on-off user of NOD32 for a while, and have recently come back from Symantec's 360 product having been fed-up with too many false positives (it seems to treat Spotify as a threat and deletes the binary - but anyway..).

    One of the reasons for heading to 360 initially was that I was experiencing the occasion very juddery video performance playing DVDs and Blu-Rays on my system (which is a Core 2 Extreme running at 2.8Ghz, 6Gb RAM and is running Windows 7. Well over 500Gb of space left on the drive). Disabling/remving Smart Security gave 100% smooth playback since.

    Looking at the CPU performance when Smart Security is running shows that CPU activity can go up to 45-60%. Comparing this to Symantec 360 this rarely went above 10%. The question is - without disabling a lot of functionality of Smart Security - what can be done to improve both the 4.2 beta so that I can have a responsive and non-jittery system?

    Mart
     
  2. mbdrake

    mbdrake Registered Member

    Joined:
    Jan 29, 2010
    Posts:
    4
    Also, I'm trying the OS X beta of NOD32 and have found that CPU usage hangs around 99% (i.e. it's taking up virtually an entire core!). Prior to this I was running Sophos and while that could slow down I/O performance a bit, it never used up as much CPU resource as this.
     
  3. guest

    guest Guest

  4. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Does performance during video playback improve after disabling real-time protection? If so, could you check the statistics window when the problem occurs to figure out which file is being continually scanned? Does setting real-time protection to scan files with pre-defined extensions instead of all files make a difference?
     
  5. agoretsky

    agoretsky Eset Staff Account

    Joined:
    Apr 4, 2006
    Posts:
    4,032
    Location:
    California
    Hello,

    Can you tell us what software you are using to play DVD and Blu-ray discs on your computer?

    Regards,

    Aryeh Goretsky
     
  6. mbdrake

    mbdrake Registered Member

    Joined:
    Jan 29, 2010
    Posts:
    4
    I used to use PowerDVD 9, but have switched to Corel WinDVD 2010 Pro. The problem can be reproduced by both products.

    I've tried disabling scanning of all files, just known extensions, and whilst CPU usage has gone down a little bit, I'm still experiencing stutter on HD playback (this time using BBC iPlayer's desktop service playing HD video) when CPU hits 100%. Unfortunately it hadn't occured to me to check what file is being scanned at the time.
     
  7. cssoz

    cssoz Registered Member

    Joined:
    Apr 11, 2009
    Posts:
    79
    this is true, a e-buddy of mine. he had to terminate NOD32 MAC OS X in order to do anything with his Macbook.

    MAC OS X 10.5.3 (or latest build of 10.5)

    2009's MacBook Pro version
     
  8. mbdrake

    mbdrake Registered Member

    Joined:
    Jan 29, 2010
    Posts:
    4
    Unfortunately I've had to give up on NOD32 on both platforms. I've tested several competitors in terms of detection success, etc. and have found a replacement AV/Security vendor which seems to utilise better CPU and still comes up well enough in the Virus Bulletin tests to be trusted.
     
  9. michael83815

    michael83815 Registered Member

    Joined:
    Jul 8, 2006
    Posts:
    39
    I have the same problem it was working fine for about two weeks but after an program update from Eset,(I have pre-release turned on) it started high cpu again. It is very frustrating. I have notice if I switch Advance Heuristics off and then reboot the high cpu goes away but when I reboot again it is high cpu again. So I turn Advanced Heuristics back on and reboot and it's gone again but on the next start up the high cpu is back. I wish they would fix this!!
     
Thread Status:
Not open for further replies.