From: Nick Piggin <piggin@cyberone.com.au>
To: Philip Martin <philip@codematters.co.uk>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.1 slower than 2.4, smp/scsi/sw-raid/reiserfs
Date: Tue, 03 Feb 2004 14:52:20 +1100 [thread overview]
Message-ID: <401F1AF4.2040205@cyberone.com.au> (raw)
In-Reply-To: <87n081vw55.fsf@codematters.co.uk>
Philip Martin wrote:
>Nick Piggin <piggin@cyberone.com.au> writes:
>
>
>
>>Philip Martin wrote:
>>
>>
>>
>>>Nick Piggin <piggin@cyberone.com.au> writes:
>>>
>>>
>>>>When the build finishes and there is no other activity, can you
>>>>try applying anonymous memory pressure until it starts swapping
>>>>to see if everything gets reclaimed properly?
>>>>
>>>>
>>>How do I apply anonymous memory pressure?
>>>
>>>
>>Well just run something that uses a lot of memory and doesn't
>>do much else. Run a few of these if you like:
>>
>>#include <stdlib.h>
>>#include <unistd.h>
>>#define MEMSZ (64 * 1024 * 1024)
>>int main(void)
>>{
>> int i;
>> char *mem = malloc(MEMSZ);
>> for (i = 0; i < MEMSZ; i+=4096)
>> mem[i] = i;
>> sleep(60);
>> return 0;
>>}
>>
>>
>
>This is what free reports after the build
>
> total used free shared buffers cached
>Mem: 516396 215328 301068 0 85084 68364
>-/+ buffers/cache: 61880 454516
>Swap: 1156664 40280 1116384
>
>then after starting 10 instances of the above program
>
> total used free shared buffers cached
>Mem: 516396 513028 3368 0 596 5544
>-/+ buffers/cache: 506888 9508
>Swap: 1156664 320592 836072
>
>and then after those programs finish
>
> total used free shared buffers cached
>Mem: 516396 35848 480548 0 964 5720
>-/+ buffers/cache: 29164 487232
>Swap: 1156664 54356 1102308
>
>It looks OK to me.
>
>
>
Yeah thats looks fine. It was a wild guess.
next prev parent reply other threads:[~2004-02-03 3:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-01 21:34 2.6.1 slower than 2.4, smp/scsi/sw-raid/reiserfs Philip Martin
2004-02-01 23:11 ` Andrew Morton
2004-02-01 23:42 ` Philip Martin
2004-02-01 23:52 ` Nick Piggin
2004-02-02 0:51 ` Philip Martin
2004-02-02 5:15 ` Nick Piggin
2004-02-02 8:58 ` Nick Piggin
2004-02-02 18:36 ` Philip Martin
2004-02-02 23:36 ` Nick Piggin
2004-02-02 23:49 ` Andrew Morton
2004-02-03 1:01 ` Philip Martin
2004-02-03 3:02 ` Nick Piggin
2004-02-03 16:44 ` Philip Martin
2004-02-03 0:34 ` Philip Martin
2004-02-03 3:52 ` Nick Piggin [this message]
2004-02-02 18:08 ` Philip Martin
2004-02-03 3:46 ` Andrew Morton
2004-02-03 16:46 ` Philip Martin
2004-02-03 21:29 ` Andrew Morton
2004-02-03 21:53 ` Philip Martin
2004-02-04 5:48 ` Nick Piggin
2004-02-04 17:50 ` Philip Martin
2004-02-04 23:38 ` Philip Martin
2004-02-05 2:49 ` Nick Piggin
2004-02-05 14:27 ` Philip Martin
2004-02-14 0:10 ` Philip Martin
-- strict thread matches above, loose matches on Subject: below --
2004-02-03 6:55 Samium Gromoff
2004-02-03 7:07 ` Andrew Morton
2004-02-03 7:52 ` Samium Gromoff
2004-02-03 7:57 ` Nick Piggin
2004-02-03 15:58 ` Valdis.Kletnieks
2004-02-03 7:13 ` Nick Piggin
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=401F1AF4.2040205@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=philip@codematters.co.uk \
/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