From: Ray Olszewski <ray@comarre.com>
To: newbie <linux-newbie@vger.kernel.org>
Subject: Re: Heavy load of graphics
Date: Mon, 04 Oct 2004 23:34:44 -0700 [thread overview]
Message-ID: <5.1.0.14.1.20041004232356.01fba510@celine> (raw)
In-Reply-To: <20041005050100.76032.qmail@web52902.mail.yahoo.com>
At 06:01 AM 10/5/2004 +0100, Ankit Jain wrote:
>hi
>
>well i am using linux 9.0 kernel 2.4 ver. 128 Mb RAM
>
>i have seen not only on this sytem but the other one
>having 512 Mb RAM the most of the memory is lost or
>taken by graphics or xserver. on my system around 90%
>is occupied by the xsever and on the sys with 512 Mb
>RAM around 70% is occupied. how to reduce this load. i
>oculd not get any article or stuff relate to this . if
>we can do something in kernel or in some way reduce
>this load while working in GUI envt
When you say "the most of the memory is lost", what exactly do you mean by
"lost"?
Any Linux system will gradually "use" 100% of available (real, not swap)
memory, by the common measures of "use", such as the diaplay in "top" or on
the first line of "free". But most of this memory (on a typical system,
anyway) is used for "cache and buffer", a jargony phrase that means, in
plain English, that Linux keeps in memory copies of recently run
executables and recently accessed data files.
You see one effect of this bit of optimizing when you run a command and it
takes a couple of seconds to run, then run it again and it runs close to
instantly. The difference, often, is that the first time, the command had
to be loaded from disk, but the second time it was cached.
But the kernel knows to make this memory available to any new processes
that need it, so it is available to users.
To see how much of your RAM is being used for cache and buffer, run "free"
and look at the entries on the second line.
OF course, all of this response is a guess. A 128 MB system running a rich
GUI like KDE might well use most of its RAM for real; here, for example,
the system I have that runs KDE really is using about 200 MB of its 768 MB
of RAM. But to be using most of 512 MB of RAM, you would have to be running
a lot of apps.
If you really are using memory with active applications, then your only
solution is to run fewer, or smaller, apps. To help at that level, we'd
need to know more of the details of how your system is set up.
PS - I'd appreciate your using standard English spellings, capitalization,
punctuation, and syntax in future postings. The shortcuts you used made it
hard for me to read your message, anough so that I almost did not take the
time to reply to it.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2004-10-05 6:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 5:01 Heavy load of graphics Ankit Jain
2004-10-05 5:45 ` Jeff Woods
2004-10-05 6:34 ` Ray Olszewski [this message]
2004-10-05 9:25 ` Geert Uytterhoeven
2004-10-05 10:04 ` Jim Nelson
2004-10-06 6:35 ` Ankit Jain
2004-10-06 21:02 ` Jim Nelson
2004-10-07 12:48 ` Ankit Jain
2004-10-07 22:00 ` Jim Nelson
2004-10-07 22:04 ` chuck gelm
2004-10-08 5:27 ` Ankit Jain
2004-10-08 14:37 ` Ray Olszewski
2004-10-05 12:26 ` chuck gelm
2004-10-05 16:25 ` Terrence Martin
2004-10-06 4:55 ` Ankit Jain
2004-10-07 1:50 ` chuck gelm
2004-10-07 2:07 ` Peter
2004-10-07 5:48 ` Ray Olszewski
2004-10-07 6:25 ` Owen Ford
2004-10-07 12:14 ` Ankit Jain
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=5.1.0.14.1.20041004232356.01fba510@celine \
--to=ray@comarre.com \
--cc=linux-newbie@vger.kernel.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