NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RN212 will not power down
RN212 with 2 12TB Seagate drives was working fine last night. Added a backup session to copy a folder from an RN528X to this RN212, which completed successfully overnight. Small transfer, only a few ...
Thanks for the update jimk1963
Interesting figures.
But it does show that having AV on, on those lower end units, is probably a bad idea.
As FileSearch brings you little value anyway, I would turn it off. I reckon when it starts to index new files you will probably see a spike in "tracker-miner" mem usage as well.
Thanks rn_enthusiast , I didn't realize indexing is only useful for the GUI-based file system. You're right of course, I never use that. Who does??? Cumbersome to say the least. I always use Windows Explorer. So I will now turn off Indexing as well as AV. This may also explain why the NAS crashed a few months ago, forcing me to reinstall the OS from USB drive. Thankfully it restored everything, but I bet the root cause of that was this memory issue. Great catch, thanks very much for combing through the logs!!!
Disabled File Indexing and AV, and rebooted machine. Ran the "top -o %MEM" command, shows that about half the memory is being used now. This command is great, it refreshes the memory usage every few seconds. With that in mind, I turned AV back on (real-time scanning and OS protection check boxes) and watched the memory usage climb from 994M to nearly 1.9G within just a few seconds. After a minute or so of watching memory usage oscillate between 1.6-1.9 GB, I turned AV back off. The memory usage dropped all the way back down to around 650 MB or so. The 3 pictures below represent these 3 states (AV/Indexing off, rebooted; AV re-enabled; AV disabled again). Strange that memory usage fell so far after re-disabling AV, but it does seem to show that enabling AV burns a hell of a lot of RAM.
AV/Indexing disabled, fresh rebootAV re-enabledAV disabled again
Also tried this on RN314, which I manuallly upgraded to 4GB RAM last year. In this case:
1) Indexing and AV both running - 90% memory used (3.6 GB) By the way, AV virus definition works fine on this box
2) Disable Indexing - no change at all to memory usage. Probably because it already completed indexing long ago, I guess
3) Disable AV - memory use dropped from 3.6GB all the way down to 2.8GB
Repeated this on RN528X with 32GB RAM:
1) 16.9GB RAM used with Indexing and AV running
2) Disabled only AV, dropped to 14.9 GB - that's 2GB RAM just for AV
3) Disabled Indexing, only another 0.6GB drop...
Seems the AV feature is quite the memory hog, if my test procedure is valid.
Thanks for the update jimk1963
Interesting figures.
But it does show that having AV on, on those lower end units, is probably a bad idea.
As FileSearch brings you little value anyway, I would turn it off. I reckon when it starts to index new files you will probably see a spike in "tracker-miner" mem usage as well.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
