Hi,
You might write a simple test to allocate all the 1K blocks that you can, count
them up, then free them. This will make sure that the 'free' memory is really
still free. It would be bad to do this in production, but it would answer the
question of whether your memory leak is just normal behavior or not. If you do
this, run it as a separate program that allocates, prints the results, and then
exits.
Mike
-----Original Message-----
>From: dawydiuk <>
>Sent: Sep 12, 2006 9:39 AM
>To:
>Subject: [ts-7000] Re: Memory leak?
>
>Hello,
>
>> Here's a summary of the free command output at 0 hours and 46 hours
>> into the test:
>>
>> used free buf cached
>> 0 hrs 15568 13304 788 8788
>> 46hrs 25004 3568 2500 10112
>>
>> You'll notice that buffer/cache allocations increase, but not nearly
>> enough to account for the decrease in free memory.
>>
>> ps listings taken at 0 and 46 hours show no appreciable change to the
>> memory allocations for processes.
>
>"The short answer is that you should never worry about the amount of
>free memory on Linux. The kernel attempts to keep this slightly above
>zero by keeping the cache as large as possible. This is a feature not
>a bug."
>
>Why doesn't free memory go down
>http://sourcefrog.net/weblog/software/linux-kernel/free-mem.html
>
>
>//Eddie
>
>
>
>
>
>
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|