From: Alexander Burnos <alex@localhost.org.ua>
To: linux-mm@kvack.org
Subject: 2.6 vs 2.4 kernel memory management question
Date: Sun, 10 Sep 2006 00:17:15 +0300 [thread overview]
Message-ID: <20060909211715.GB3829@leeloo.source.org.ua> (raw)
Hello!
Sorry if it's not appropriate mail list for this question if it's so,
please, point me to the correct place to ask.
I have several linux (debian) servers with java applications each of
them takes, for examples, 200 mbyte of RAM. I've noticed that on
machines with 2.4 kernels VIRT and RES memory (accordinly to 'top'
values) are equal. So top shows me that VIRT == RES == 200 mbyte
(approximately).
But! On the servers with 2.6 kernel I have another picture, VIRT memory
in several times bigger than RES. For example real memory of java
proccess is 146 mbytes, but virtual - 470 mbytes.
At the firt look it isn't a problem, but when I have several java
processes and summary of their virtual memory is more than physical
memory on the server - operatin system begin swapping although there is
30-50% of free memory (2 Gbyte memory on each machine).
At the end we have machine that fall into hard swapping when big part of
memory is actually free.
I've tried to play with "echo 0 > /proc/sys/vm/swappiness" but it didn't
give me good results.
Please, point me to doc where I can read about "physics" of this process
and where I can make some tunning to avoid this effect of growing
virtual memory on 2.6 kernels?
Maybe, it depends on the difference between NPTL and linuxthreads
realization?
Thank you for your answers!
--
WBR,
Alexander Burnos
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
reply other threads:[~2006-09-09 21:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060909211715.GB3829@leeloo.source.org.ua \
--to=alex@localhost.org.ua \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox