From: Hans Reiser <reiser@namesys.com>
To: David Dabbs <david@dabbs.net>
Cc: 'Alex Zarochentsev' <zam@namesys.com>,
'Elena Gryaznova' <grev@namesys.com>,
reiserfs-list@namesys.com
Subject: Re: mongo benchmark results
Date: Mon, 26 Jul 2004 12:18:20 -0700 [thread overview]
Message-ID: <410558FC.40204@namesys.com> (raw)
In-Reply-To: <20040726173552.20ECA15EBD@mail03.powweb.com>
David Dabbs wrote:
>>-----Original Message-----
>>From: Alex Zarochentsev [mailto:zam@namesys.com]
>>Sent: Monday, July 26, 2004 12:09 PM
>>
>>2 Lena:
>>
>>I have added a cpu utilization stat (ratio of system time for all cpus to
>>total time, in percents) to mongo.pl.
>>
>>Please take new mongo before repeating the benchmark.
>>
>>--
>>Alex.
>>
>>
>
>For what it's worth, I reproduced the mongo runs with 8k files as Hans
>suggested. Results are at
>
>http://dabbs.net/reiser4/mongo8kfiles.html
>
>The CREATE performance increase seems to have evaporated, though perhaps
>that was what Hans was looking to test with the updated config. I was in a
>hurry this morning and I may have varied the test slightly. I'll use Zam's
>new mongo when I get home this evening. I will as well test copying and
>compiling the kernel. Unless there's another recommended way to do this, I
>I'll substitute the output from "time -c" into a mongo log file so
>mongo_parser can compare the results.
>
>Zam/Elena where should I look for the new mongo tgz? I don't see it at
>http://thebsh.namesys.com/benchmarks/.
>
>Thanks for the updated mongo.
>
>david
>
>
>
>
>
>
>
Ignore what I said about 500mb mongo, the dd gives the info desired.
I don't understand these results. If they are correct, we have lost a
lot of our ext3 performance advantage, and I want to know where it
went. Elena, Zam, please comment.
next prev parent reply other threads:[~2004-07-26 19:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 5:49 mongo benchmark results David Dabbs
2004-07-26 6:48 ` Hans Reiser
2004-07-26 8:24 ` Nikita Danilov
2004-07-26 8:43 ` Alex Zarochentsev
2004-07-25 8:21 ` Nikita Danilov
2004-07-26 11:01 ` Alex Zarochentsev
2004-07-26 8:54 ` Alex Zarochentsev
2004-07-26 17:08 ` Alex Zarochentsev
2004-07-26 17:31 ` David Dabbs
2004-07-26 19:11 ` Hans Reiser
2004-07-26 19:45 ` David Dabbs
2004-07-26 19:18 ` Hans Reiser [this message]
[not found] ` <41056FFF.4010208@namesys.com>
[not found] ` <4105FDFA.1090308@namesys.com>
[not found] ` <410833F9.501@namesys.com>
2004-07-29 7:31 ` Reiser4 slowed down, Elena has found the changesets responsible, we will fix it Hans Reiser
[not found] ` <20040729152103.GN4881@backtop.namesys.com>
[not found] ` <410A57C6.3020501@namesys.com>
2004-07-30 18:28 ` Reiser4 performance is almost completely restored now Hans Reiser
2004-07-26 19:41 ` mongo benchmark results E. Gryaznova
2004-07-26 20:00 ` David Dabbs
2004-07-26 20:06 ` E. Gryaznova
2004-07-29 3:13 ` David Dabbs
2004-07-30 15:16 ` E. Gryaznova
2004-07-30 16:11 ` David Dabbs
2004-07-30 18:57 ` Reiser4 performance is almost completely restored now David Dabbs
2004-07-30 19:01 ` Alex Zarochentsev
2004-07-30 20:37 ` Unattended mongo benchmark? David Dabbs
2004-07-31 5:19 ` Hans Reiser
2004-07-31 11:00 ` Nikita Danilov
2004-07-31 14:16 ` David Dabbs
2004-07-30 21:46 ` Nikita Danilov
2004-07-31 14:46 ` Vladimir V. Saveliev
2004-07-30 21:59 ` Nikita Danilov
2004-07-31 15:13 ` David Dabbs
2004-07-31 16:48 ` Vladimir V. Saveliev
2004-07-27 7:20 ` mongo benchmark results Hans Reiser
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=410558FC.40204@namesys.com \
--to=reiser@namesys.com \
--cc=david@dabbs.net \
--cc=grev@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=zam@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.