From: Lorenzo Allegrucci <lenstra@tiscalinet.it>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VM: qsbench
Date: Wed, 31 Oct 2001 18:55:23 +0100 [thread overview]
Message-ID: <3.0.6.32.20011031185523.01fc2d30@pop.tiscalinet.it> (raw)
In-Reply-To: <3BDFED26.4350646B@mandrakesoft.com>
In-Reply-To: <3.0.6.32.20011031131253.01fb8e40@pop.tiscalinet.it>
At 07.23 31/10/01 -0500, Jeff Garzik wrote:
>Lorenzo Allegrucci wrote:
>> Linux-2.4.14-pre6:
>> lenstra:~/src/qsort> time ./qsbench -n 90000000 -p 1 -s 140175100
>> Out of Memory: Killed process 224 (qsbench).
>> 69.890u 3.430s 2:12.48 55.3% 0+0k 0+0io 16374pf+0w
>> lenstra:~/src/qsort> time ./qsbench -n 90000000 -p 1 -s 140175100
>> Out of Memory: Killed process 226 (qsbench).
>> 69.550u 2.990s 2:11.31 55.2% 0+0k 0+0io 15374pf+0w
>> lenstra:~/src/qsort> time ./qsbench -n 90000000 -p 1 -s 140175100
>> Out of Memory: Killed process 228 (qsbench).
>> 69.480u 3.100s 2:13.33 54.4% 0+0k 0+0io 15950pf+0w
>> 0:01 kswapd
>>
>> This is interesting, -pre6 killed qsbench _just_ before qsbench exited.
>> Unreliable results.
>
>Can you give us some idea of the memory usage of this application? Your
>amount of RAM and swap?
256M of RAM + 200M of swap, qsbench allocates about 343M.
--
Lorenzo
prev parent reply other threads:[~2001-10-31 17:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-31 12:12 Lorenzo Allegrucci
2001-10-31 12:23 ` Jeff Garzik
2001-10-31 15:00 ` new OOM heuristic failure (was: Re: VM: qsbench) Rik van Riel
2001-10-31 15:52 ` Linus Torvalds
2001-10-31 16:04 ` Rik van Riel
2001-10-31 17:42 ` Stephan von Krawczynski
2001-10-31 18:22 ` Linus Torvalds
2001-10-31 17:55 ` Lorenzo Allegrucci
2001-10-31 18:06 ` Linus Torvalds
2001-10-31 21:31 ` Lorenzo Allegrucci
2001-11-02 13:00 ` Stephan von Krawczynski
2001-11-02 17:36 ` Lorenzo Allegrucci
2001-10-31 17:55 ` Lorenzo Allegrucci [this message]
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=3.0.6.32.20011031185523.01fc2d30@pop.tiscalinet.it \
--to=lenstra@tiscalinet.it \
--cc=jgarzik@mandrakesoft.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®