Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 7 replies
  • Subscribers 1 subscriber
  • Views 3695 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

AV for Mac and Matlab

BobWhite

We have a Mac OS X 10.6 workstation that we recently installed the AntiVirus on.  The WS is used to run numerical processing apps that are generated from Matlab.  The apps rely on parallel processing to improve performance.  When the apps start up they open a large number of files, many of them quite large.  With the AV installed the processing slows to a crawl, and almost to a stand still.  Is there some way to set AV so it doesn't scan a app or any files that app may open?

:18975


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

    Hello BobWhite,

    you can define exclusions for files, folders and volumes but not for an app or a process (i.e. all files opened by a certain app/process). Usually the files are not scattered all over the file system so excluding one or two folders and their subfolders should suffice. If performance is still not satisfactory I'd consider turning off on-access scanning during number crunching. As you can control on-access scanning with AppleScript you could automate disabling/enabling it.

    Scanning always incurs a performance loss and turning off scanning (even partially) always incurs some additional risk. I know, ideally there should be a Scanner's demon which would only scan when and where a threat is present - but this would probably violate some fundamental law of IT :smileywink:

    Christian   

    :19049
Reply
  • 0

    Hello BobWhite,

    you can define exclusions for files, folders and volumes but not for an app or a process (i.e. all files opened by a certain app/process). Usually the files are not scattered all over the file system so excluding one or two folders and their subfolders should suffice. If performance is still not satisfactory I'd consider turning off on-access scanning during number crunching. As you can control on-access scanning with AppleScript you could automate disabling/enabling it.

    Scanning always incurs a performance loss and turning off scanning (even partially) always incurs some additional risk. I know, ideally there should be a Scanner's demon which would only scan when and where a threat is present - but this would probably violate some fundamental law of IT :smileywink:

    Christian   

    :19049
Children
No Data