DNS-320L - High Memory usage, file transfer issues.

[Steve]

Hi - I have a DNS-320L that's having issues.  I am running the latest ALT-F (RC5) with 2x2tb WD Greens Raid 1.  Services - Transmission, miniDNLA, SMB, NFS, FTP.  

My memory usage with everything except core services, SMB and FTP disabled when restarted is fine, when I start copying via SMB or downloading a file with FTP, my memory usage goes back up to 97-98% and I get issues during the next transfer.

Any ideas?

I went to this NAS from a 323 in hopes to be able to run owncloud in addition to miniDLNA and Transmission.

[João Cardoso]

On Friday, 5 May 2017 17:03:32 UTC+1, Steve wrote:

Hi - I have a DNS-320L that's having issues.  I am running the latest ALT-F (RC5)

network fix applied?

 

with 2x2tb WD Greens Raid 1.  Services - Transmission, miniDNLA, SMB, NFS, FTP.  

My memory usage with everything except core services, SMB and FTP disabled when restarted is fine, when I start copying via SMB or downloading a file with FTP, my memory usage goes back up to 97-98%

Most OS use fast memory for caching files or programs access (buffer and page caches), so it is normal that after being used for a while the in use memory tops. That is linux FAQ.

[Steve]

Didn't try the network fix, but I rolled back to 4.1 and saw no change.  I understand that whatever spare memory memory is being used for cache, but shouldn't it release it after the transfer is done?  After copying a file it sticks the memory at 98% and doesn't release it until I reboot the NAS.

[João Cardoso]

On Friday, 5 May 2017 17:33:08 UTC+1, Steve wrote:

Didn't try the network fix, but I rolled back to 4.1 and saw no change.  I understand that whatever spare memory memory is being used for cache, but shouldn't it release it after the transfer is done?

No, you or somebody else could need the file again sooner -- that is what cache is, and cached data is valid while the disk file exists.

But that does not applies only to user files, but also to programs and its data-- they run in memory, so they are loaded from disk and cached, even if the program terminates -- you might start it again soon.

You should not worry with the memory usage -- that's an OS thing. But if "swap" starts being consistently used, then you should ponder if you really need all the programs that you are running, or if some of them got out of control. "swap" does the reverse that caching does -- more memory is needed than it is available, and disk starts being used to simulate the missing memory, only thousands of times slower.

[Steve]

João:

If it normal that way I'll try the network fix.  I thought the file transfer and memory usage were possibly related.  Thanks.

[braste49]

Hi,

I have the same NAS, in version 1.0 (network fix included), and with Samba only (not mini dlna), I'm in 90% every time.

How I can know which process is concerned ? "ps -eaf" is not working...

Thanks a lot for your help...

[João Cardoso]

On Sunday, 8 December 2019 08:24:29 UTC, braste49 wrote:

Hi,

I have the same NAS, in version 1.0 (network fix included)

for 1.0 you don't need the network fix applied, it was only needed for RC5 and it will slightly degrade throughput, remove it.

 

, and with Samba only (not mini dlna), I'm in 90% every time.

How I can know which process is concerned ? "ps -eaf" is not working...

System->utilities, View Logs, Running Processes

For high memory usage, the VSZ (MB) and %VSZ columns show you the amount of virtual memory used by each process. If greater than 100% it means that swap is being used.

For high CPU usage the column to examine is %CPU

If none of the above is worrying and it is the high "memory" usage in the Status Page that worries you, that is normal, memory is being used, that's what for what it was made.

If it is low throughput (2-5MBps) that worries you, make sure  that wifi is not being used between the box and your PC, and/or that you are not using any 'S' (secure) protocol such as ssh, fts2/sftp, encryption, etc