From: "Ihar 'Philips' Filipau" <filia@softhome.net>
To: Roger Luethi <rl@hellgate.ch>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [OT] No Swap. Re: [BUG 2.6.90-test5] kernel shits itself with 48mb ram under moderate load
Date: Sun, 28 Sep 2003 15:06:52 +0200 [thread overview]
Message-ID: <3F76DCEC.60508@softhome.net> (raw)
In-Reply-To: <20030927202148.GA31080@k3.hellgate.ch>
Roger Luethi wrote:
> On Sat, 27 Sep 2003 21:59:55 +0200, Ihar 'Philips' Filipau wrote:
>
>> Better than with swap. This is production workstation - I cannot test
>>something on it :-(
>
>
> I don't think there's much risk involved in running 2.[56]. If it doesn't
> boot, you can go back to 2.4. If it does boot, it won't eat your data.
> YMMV, of course.
>
Data corruption? My back-up of work?
I cannot back-up my data since my comp by itself is backup :-)
>
>> <rant>'Paging like crazy' became for me a synonym of Linux. It
>>doesn't matter how much memory you have. Less == worse. Developers
>
>
> Oh, it does matter. My workstation has 1 GB RAM and 2 GB swap and I hardly
> see any problems with paging <g>.
>
Because your workload doesn't hit the 1GB limit.
Actually we just do not have fast enough I/O + CPU to utilize 1GB of
RAM efficiently.
But if you will go into 128MB of RAM - you will see difference, where
should be no difference.
Let's say (my personal exp.) cp'ing of kernel source with 0.5/0.25 GB
RAM dosn't differ. Aproximately the same time. 0.25GB little bit faster
- but it can be written off to noise. But try to do the same cp with
0.125GB - this cp (as of RH 2.4.20-20.9 +ext3 -swap) takes _*two*_ times
longer. Should it be?
>
>>stopped testing VMM regression on low-memory computers long time ago.
>
> Many of the best Linux devs these days work for companies and organizations
> that are in the business of selling or using big iron. They have people on
Indeed.
--
Ihar 'Philips' Filipau / with best regards from Saarbruecken.
--
"... and for $64000 question, could you get yourself vaguely
familiar with the notion of on-topic posting?"
-- Al Viro @ LKML
next prev parent reply other threads:[~2003-09-28 13:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ArQ0.821.23@gated-at.bofh.it>
[not found] ` <ArQ0.821.25@gated-at.bofh.it>
[not found] ` <ArQ0.821.21@gated-at.bofh.it>
[not found] ` <ArZC.8f1.9@gated-at.bofh.it>
2003-09-27 19:59 ` [OT] No Swap. Re: [BUG 2.6.90-test5] kernel shits itself with 48mb ram under moderate load Ihar 'Philips' Filipau
2003-09-27 20:13 ` William Lee Irwin III
2003-09-27 20:25 ` Roger Luethi
2003-09-29 5:02 ` Nick Piggin
2003-09-29 5:08 ` William Lee Irwin III
2003-09-27 20:21 ` Roger Luethi
2003-09-28 13:06 ` Ihar 'Philips' Filipau [this message]
2003-09-28 15:52 ` Mikulas Patocka
2003-09-28 17:21 ` Ihar 'Philips' Filipau
2003-09-28 17:31 ` Mikulas Patocka
2003-09-28 17:54 ` Ihar 'Philips' Filipau
2003-09-28 18:04 ` William Lee Irwin III
2003-09-28 17:33 ` Mr. James W. Laferriere
2003-09-28 17:57 ` Ihar 'Philips' Filipau
[not found] <Apl1.4ur.9@gated-at.bofh.it>
[not found] ` <Ar3B.6UW.21@gated-at.bofh.it>
2003-09-27 18:13 ` Ihar 'Philips' Filipau
2003-09-27 18:27 ` Roger Luethi
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=3F76DCEC.60508@softhome.net \
--to=filia@softhome.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rl@hellgate.ch \
/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;
as well as URLs for NNTP newsgroup(s).