From: Oliver Neukum <oliver@neukum.org>
To: Karl Vogel <karl.vogel@seagha.com>, linux-kernel@vger.kernel.org
Subject: Re: How do I make this thing stop laging? Reboot? Sounds like Windows!
Date: Wed, 18 Jun 2003 18:53:22 +0200 [thread overview]
Message-ID: <200306181853.22687.oliver@neukum.org> (raw)
In-Reply-To: <6DED3619289CD311BCEB00508B8E13360117748D@nt-server2.antwerp.seagha.com>
Am Mittwoch, 18. Juni 2003 11:56 schrieb Karl Vogel:
> > > Swap prefetching? If you have >10% free physical ram and
> >
> > any used swap it
> >
> > > will start swapping pages back into physical ram. Probably
> >
> > not of real
> >
> > > benefit but many people like this idea. I have a soft spot
> >
> > for it and like
> >
> > > using it.
> > > --
> > >
> > > The disadvantage is ofcourse that you will be using up more
> >
> > RAM than is
> >
> > > really necessary.
> >
> > No, free RAM is wasted RAM.
>
> But the point is, it's not really free RAM. It's being used for
> I/O caching. So while swap prefetching might be suited for
> desktop systems, it certainly isn't for servers.
Not entirely. Have a look:
oliver@vermuden:~> free
total used free shared buffers cached
Mem: 514844 501652 13192 0 130124 216476
-/+ buffers/cache: 155052 359792
Swap: 1036152 6120 1030032
oliver@vermuden:~> free
total used free shared buffers cached
Mem: 514844 500500 14344 0 119940 224772
-/+ buffers/cache: 155788 359056
Swap: 1036152 6584 1029568
oliver@vermuden:~>
This is before starting OpenOffice and after quitting it.
As you can see the amount free RAM really goes up. This RAM is wasted.
It will eventually be put to use, but there's nothing wrong with speeding
this up. Reading back swap is almost certainly not the optimum way to
use it, but it's better than nothing at all, provided the RAM is not tied up.
The question is whether it's worth it in terms of IO.
Regards
Oliver
next prev parent reply other threads:[~2003-06-18 16:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 9:56 Karl Vogel
2003-06-18 16:53 ` Oliver Neukum [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-18 10:49 Karl Vogel
2003-06-18 10:43 Karl Vogel
2003-06-18 0:30 rmoser
2003-06-18 8:22 ` Helge Hafting
2003-06-18 9:22 ` Karl Vogel
2003-06-18 9:44 ` Oliver Neukum
2003-06-18 10:23 ` Anders Karlsson
2003-06-18 15:08 ` Gianni Tedesco
2003-06-18 16:43 ` Joe
2003-06-18 9:30 ` Yaroslav Rastrigin
2003-06-18 11:02 ` Helge Hafting
2003-06-18 12:17 ` Mike Galbraith
2003-06-19 8:04 ` H. Peter Anvin
2003-06-19 10:00 ` Helge Hafting
2003-06-19 10:02 ` Nick Piggin
2003-06-19 15:54 ` Daniel Gryniewicz
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=200306181853.22687.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=karl.vogel@seagha.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®