2009년 7월 27일 월요일 오전 4:50
FSEContentScanner.exe is using a constant 191,000 K of memory. Combined with the other process like AntigenInternet.exe that are low now, but were each running 140,000 K a piece before, I've got a situation where I'm seeing system slowdown (4GB memory) because of this software and all I'm running is Exchange 2003 with 25 users.
2009년 7월 30일 목요일 오후 6:13Hi,
I'd suggest lowering the real time process count and/or internet process count process that will be used. Remember that you need a minimum of 1GB of free memory to run antigen (excluding the memory that exchange needs to run). An other option is to lower the number of scan engines.
2009년 8월 6일 목요일 오전 12:08
Antigen version 9 with Service Pack 2 incorporates new anti-spam technology through a partnership with Cloudmark that provides an overall better anti-spam experience including higher detection rates, lower false positives, an improved submission experience, and enhanced service experience. The solution integrates with the Antigen product in much the same manner as any other engine, with a few exceptions.
• The Cloudmark anti-spam engine receives its signature updates directly from the vendor’s site and not through Microsoft. • The signature updates are not configurable in the Antigen administrator, as the other scan engine updates are. • Cloudmark uses the FSEContentScanner.exe process to pull the signature updates. This will use approximately 80 MB initially, then it will use an average of between 80 MB to 150 MB spread out over a 24-hour period, so that you will see only a small amount of bandwidth used every minute. • The engine updates for the Cloudmark anti-spam engine are configurable in the Antigen administrator, exactly like the other scan engine updates.
2009년 8월 11일 화요일 오후 2:47I'll second robaht's and John's recommendations above.
As of the SP2 package, there are now 8 (!) A/V engines that Antigen uses, and all are enabled by default out of the box. Further, it is still configured to use 2 processes by default. Both of these issues can potentially cause HUGE resource problems <no available memory causing server crashes>, especially on multi-core CPU's. If you have a quad core CPU, it will allocate 1 process for EACH core, not just a single CPU, so if you're at 2-processes in antigen, you're actually getting 8 processes running for Antigen, each taking ~200MB of memory <on our systems, anyway...>. (Check task mgr to see this in action.)
After you install, I'd recommend (as above) turning down the default processes to just 1, and disabling a number of the engines to preserve processing resources. I've disabled the Norman, Authentium and the 'Microsoft Antimalware' engines on my systems, and haven't had a repeat of the memory resource crashes.
Antigen 9.0 SP2
HP DL 585 Quad Core
2009년 11월 4일 수요일 오후 11:36I have come to this thread looking for why the Cloudmark is using so much CPU and memory.
It has turned a old ML 350 G4 into a roaring jet engine as the Cloudmark FSEContentScanner.exe chews up those cycles and memory.
This old box was ticking along fine with SpamCure and 1 RBL, nil phishing/spam. I really shows up the performance hit of Cloudmark.
Is there going to be an 'optimize' Best Practices tool produced for ForeFront and Antigen....please make it have recommendations for 'A = Best Performance' and 'B = Highest security'. This would need to swing in straight after the original install or SP upgrade.
The current defaults for ForeFront in Essential Business Server and Antigen for Exchange are giving the product bad responses...I recommend it to an admin and they complain about huge downloads and poor performance...How about building a 'performance wizard'?
Computer: Model: ProLiant ML350 G4(HP) Processor: 2*Xeon(TM) 3000MHz (L1 cache: 0 bytes, L2 cache: 1.00 Mb) Ext.clock: 800 MHz
Memory: 4.00 Gb DDR,Synchronous,3.0 ns Hard disks: 69.5 Gb primary disk