Re: Copying large files eats all of the RAM

[Andreas Mohr <andi@lisas.de>]

On Sat, Nov 30, 2013 at 11:59:07AM +0530, venkata koppula wrote:
> Thanks for you replies.
> 
> Yeah, I understand that we need to utilize the resources as much as we
> can. At the same time user should not
> feel that system is slow and user should never wait for the copying
> operation should complete to launch another
> application meanwhile.
> 
> If the user is a system administrator or a programmer, he/she
> understands the problem and will try to tune the kernel
> based on his/her requirements. As an application user(A desktop user
> doesn't worry about the optimizations,
> even doesn't know what it is:)) faster response is important.

I'm afraid you're damn right - standard configuration ought to be pretty
similar to the optimum, without any tuning, given that most people don't
(know to) do manual tuning.
And even in recent times the kernel did not manage to achieve that goal,
for several use cases. But I'm quite certain we're getting closer :)

BTW, a quite likely related and possibly helpful topic is
"[patch 7/9] mm: thrash detection-based file cache sizing" https://lkml.org/lkml/2013/12/2/483

HTH,

Andreas Mohr

-- 
GNU/Linux. It's not the software that's free, it's you.