yochenhsieh Posted July 17, 2019 Report Share Posted July 17, 2019 (edited) Hello, I just installed immunet for first time, and after system boot up sfc.exe consumes more than 700 MB memory. Is there any way to reduce memory usage? If I disable clamAV engine and it will use about 35~60MB RAM. Edited July 17, 2019 by yochenhsieh Link to comment Share on other sites More sharing options...
ritchie58 Posted July 18, 2019 Report Share Posted July 18, 2019 That definitely is excessive RAM usage! What is your Operating System and what version of Immunet are you currently using? Just mouse over 'About' on the lower right side of the UI and that will tell you what build you're using. Was Immunet running any scheduled or manually launched scan during that time of excessive RAM usage? Do you have any programs that very frequently or constantly write to disk such as a backup OS shadow copy or similar software package? Link to comment Share on other sites More sharing options...
yochenhsieh Posted July 18, 2019 Author Report Share Posted July 18, 2019 (edited) Operation System: Windows 7 SP1, with latest KB updates. Immunet version: 6.3.0.10988 No. I'm not using scheduled or manual scan at the time of high memory usage. These are my programs that may have high file/disk io, but I'm not using any of them at the time of high memory usage: firefox, virtualbox, qbittorrent, mipony. Today I noticed memory usage with clamAV enabled has dropped to ~183MB (when only using firefox typing this post). But I think it's still too high compared with other antivirus products. [EDIT] After using PC for some time and closing all programs, Immunet still uses ~442MB. Edited July 18, 2019 by yochenhsieh Link to comment Share on other sites More sharing options...
ritchie58 Posted July 19, 2019 Report Share Posted July 19, 2019 I see you're using Oracle's VirtualBox software. That might be the problem. Other users have run into serious issues while trying to use Immunet in a Virtual Machine environment in the past. Although not entirely impossible and depending on the software it usually takes lots of tweaking with the VM software to get Immunet to function properly. Link to comment Share on other sites More sharing options...
yochenhsieh Posted July 19, 2019 Author Report Share Posted July 19, 2019 I think the problem is caused by the clamAV engine. If I disabled clamAV engine, memory usage drops significantly. If there's any way to assist debugging this issue, I'm willing to help. Otherwise, I think I'll keep clamAV engine disabled. Link to comment Share on other sites More sharing options...
ritchie58 Posted July 20, 2019 Report Share Posted July 20, 2019 If you think the issue is with the ClamAV engine & not a conflict between Immunet (ClamAV disabled) and your VM software might I suggest you contact the ClamAV team directly at this URL. https://www.clamav.net/contact Perhaps they can assist you further. Link to comment Share on other sites More sharing options...
Rob.T Posted July 31, 2019 Report Share Posted July 31, 2019 Immunet doesn't have any know issues running in virtualized environments and has been thoroughly tested in vmware workstation, vmware server and virtual box. and once even in Microsoft's cloud. Complaints we've gotten about running in visualized environments usually stem from unrealistic expectations of performance on non-dedicated hardware (i.e. cloud hardware thats randomly shared with strangers (e.g. the free trial and budget tier's of google, amazon and Microsoft clouds). There is just too high a chance someone like me is sharing hardware time and already pushing the machine to it' s limits (see paragraph below:) To set some hardware expectations, I test Immunet on a local desktop running dual xenon e506 2.13Ghz CPU's +12 gb ram (ouch), and 2 independent scsi 1TB drives ( one dedicated to my os & apps, the other dedicated to vmware images) and it easily simultaneously powers my win10 working desktop (chrome, waterfox, and IE browsers, email, visual studio, and an Android Virtual device) plus 3 copies of immunet running on vmware workstation images for win7x32, win7x64, & xpx32. It can also power an additional win 10x64, but at this point the images start to chug ( I think disk bandwidth is the bottleneck). I can easily run this same level of compute (dektop + 4 images) + an additional win10_x64 image on a single more modern Intel i-core 7 + 64gb of ram and 2 sata disks (one flash drive for the OS & apps an a 1tb 7200 rpm disk for the images). Getting back to your original problem, yochenhsieh you nailed it figuring out clamAV, I've seen similar stats with my benchmarking too. The clam av engine loads it's full virus definitions signature set into memory: which takes from 100 to 600mb. add to that the clam scanning engine and virus definitions updater and clam alone can in a worst case scenario use in the the 700mb of memory range. Currently we have extra experimental blue keep preventative signatures out for a worm we're expecting that are inflating the usual virus definitions set size. You can try updating the clam av definitions set via the update button in the gui and running a full scan overnight. That might get you a smaller more concise set of definitions that'll take less memory and get you over the initial performance hump of building the local cache up. 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now