Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

SAV for NAS performance tuning tips / Java tuning?

Created: 25 Oct 2011 • Updated: 26 Oct 2011 | 4 comments
waphil00's picture

 

Dear All,

I was just wondering if there is a need to tune the default Java installation on a Symantec SAV for NAS installation and if somebody has experience with different memory tuning values.

Typical setup would be Windows 2008 R2 with 4GB RAM and Java runtime version 6 with RPC connection to a Netapp storage.

The following I did already:

  • Tuning of the TCP settings, added MaxUserPorts with a value of 60000
  • Set a timeout on the netapp if scan takes too long (vscan options abort_timeout set 50  and vscan options mandatory_scan off)
  • Created a inclusion list on the netapp to scan only "dangerous files" (vscan options include)
  • Have the SAV for NAS servers on dedicated 1Gbit interfaces connected to the Netapp on a dedicated switch.
  • Use two redundant SAV servers for load balancing. (the netapp will do a automatic round robin type of LB)

Questions:

  • Is SAV for NAS faster on Windows or on Linux?
  • Does it help to do some Java tuning? and if yes, which values should be changed?
  • Is it recommended to run the direct link to the storage with Jumbo frames?
  • Are shorter timeout values on the netapp recommended?
  • Any other tuning tips?

 

Thanks for any input.

- philipp

Comments 4 CommentsJump to latest comment

BenDC's picture

We are quite limited as to the tuning advise we can prodive due to so many variables such as the machine with the scan engine it self, the network configurations, and average filesize, etc. Below I have linked to the Best Practices document for the SAV fo NAS with a NetApp Filer.

Best Practices for implementing Symantec AntiVirus for Network Attached Storage with a NetApp Filer: http://www.symantec.com/business/support/index?pag...

waphil00's picture

Thank you for the link. 

For all those reading my initial post: I ended up leaving the Java settings as they are but I changed the resource settings within the SAV for NAS console:
 

 

Go to configuration --> resources (if you cant see this menu you have to expand/slide the row next to configuration) --> "number of available threads for scanning": If you have many CPU cores you might want to increase this value from its initial value of 128 to lets say 256 but I think also the initial value is fine.

"Maximum RAM used for in memory file system", I recommed to increase to 512 mb or more, in general a value that suits your systems RAM specs. Without testing it I would be careful to go above 1-2 Gbyte.

"Maximum file size stored within the in memory file system": increase to 96 mb or something that is balanced between the file sizes you expect and the RAM you have available for scanning. This value should probably be lower than the "Maximum RAM used for in memory file system".

 

regards

philipp

JJP's picture

 

Questions:

  • Is SAV for NAS faster on Windows or on Linux?
  • Does it help to do some Java tuning? and if yes, which values should be changed?
  • Is it recommended to run the direct link to the storage with Jumbo frames?
  • Are shorter timeout values on the netapp recommended?
  • Any other tuning tips?

 

from what I know:

linux is between 10/15% faster, but you cant do RPC on it if I remember corectly.

Java tuning is also factored by the OS - yes on older windows servers, less so on 2008r2 etc.

jumbo frames and such depends on your data types, if by direct connect you mean crossover cable etc. If your on a crossover cable or single connection via an non roted network device I'd expect a very minimal gain from jumbo frames and probably a lot of issues from anything else sharing the network if they are sensitive to this setting.

I'd likewise like to know about the netapp timing options.

Fast disk IO.

BenDC's picture

You are correct Scan Engine cannot do RPC on linux or solaris.