Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 10 replies
  • Subscribers 1 subscriber
  • Views 28905 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Best practice for on-access scanning

Jvuz

Hi,

we're having some older computers who are experiencing some problems. Their machines are extremely slow when using the default on-access settings. From the moment we disable the on-access scanning, the computers work without any problem. As it's not done to let it disabled, I'm looking for a way to set it for those computers that they're safe but also that they can keep working. What are your suggestions?

Jo

:57558


This thread was automatically locked due to age.
Parents
  • 0

    Hello Jo,

    wish it'd be that simple. I'd first try to assess the exact nature of slow - are all actions (perceived as) slow or only certain ones. From the configuration data I'd rule out memory as the bottleneck (but I might be wrong).

    Using Sysinternal's Process Explorer I'd have a look at CPU usage, whether CPU is high (at certain) times and if which process is responsible. Still in ProcExp - opening the Properties of SavService.exe and tabbing to Performance Graph will show whether SavService's activity correlates with the foreground actions - if not, then "something" in the background is accessing lots of files.

    Keep in mind that On-Access is kinda electronic monkey requesting a scan when a file is about to be opened - no opens and nothing to do for On-Access. Turn off On-Access and check what changes.

    Next steps depend on your findings ...

    Christian

    :57604
Reply
  • 0

    Hello Jo,

    wish it'd be that simple. I'd first try to assess the exact nature of slow - are all actions (perceived as) slow or only certain ones. From the configuration data I'd rule out memory as the bottleneck (but I might be wrong).

    Using Sysinternal's Process Explorer I'd have a look at CPU usage, whether CPU is high (at certain) times and if which process is responsible. Still in ProcExp - opening the Properties of SavService.exe and tabbing to Performance Graph will show whether SavService's activity correlates with the foreground actions - if not, then "something" in the background is accessing lots of files.

    Keep in mind that On-Access is kinda electronic monkey requesting a scan when a file is about to be opened - no opens and nothing to do for On-Access. Turn off On-Access and check what changes.

    Next steps depend on your findings ...

    Christian

    :57604
Children
No Data