eScan Blog
eScan Website
eScan Forum
eScan Feeds From eScan Wiki
(Difference between revisions)
| Revision as of 08:35, 5 June 2009 WikiSysop (Talk | contribs) ← Previous diff |
Revision as of 08:05, 9 June 2009 WikiSysop (Talk | contribs) Next diff → |
||
| Line 1: | Line 1: | ||
| - | |||
| <B>Q. Will eScan cause instability & performance hit?</B> | <B>Q. Will eScan cause instability & performance hit?</B> | ||
| Line 6: | Line 5: | ||
| Please note however that the anti-virus & any Content-Check components of eScan do use CPU resources & RAM.</I> | Please note however that the anti-virus & any Content-Check components of eScan do use CPU resources & RAM.</I> | ||
| + | |||
| + | |||
| + | ---- | ||
| + | <B><I><font size=2>Email us your feedback to [mailto:solutions@mwti.net solutions@mwti.net]</font></I></B> | ||
Revision as of 08:05, 9 June 2009
Q. Will eScan cause instability & performance hit?
A. Since eScan works well above the "raw-packet" layer, MS-MWL - on its own - should not cause any instability and/or performance hit.
Please note however that the anti-virus & any Content-Check components of eScan do use CPU resources & RAM.
Email us your feedback to solutions@mwti.net
