[Dirvish] large memory footprint

Arash Abghari arash.abghari at gmail.com
Fri Aug 31 03:56:17 UTC 2012


On 30/08/12 11:25 PM, Arash Abghari wrote:
> Hi,
>> 'free' output is not really very good indication. I think you should
>> subtract the unused buffer space (13945).
>> I think what's happening is that the dirvish run reads a lot of data
>> from the disk and uses up 13GB of buffer space, which is still 'hot'
>> after dirvish terminates---the system has no way of knowing that you
>> won't need that again soon, so it's not discarded right away, but
>> will be dropped as soon as the buffer space is needed.
>>
>> cat /proc/meminfo  is a better, more detailed summary of what's in 
>> your memory.
>>
> /proc/meminfo repots the same memory usage as free does.
> According to this 
> http://www.linuxquestions.org/questions/linux-server-73/rsync-hogs-memory-758345/ 
> thraed, it is related to rsyncing large directory tree and inodes 
> buffer and the memory can be claimed by issueing  "sync; echo 2 > 
> /proc/sys/vm/drop_caches". It did indeed solve my high memory usage 
> problem.
>
> Thanks,
>
> Arash

take a look at this thread 
http://lists.samba.org/archive/rsync/2010-April/024992.html as well. It 
describes the problem with more details.




More information about the Dirvish mailing list