From: "E. Gryaznova" <grev@namesys.com>
To: David Dabbs <david@dabbs.net>
Cc: reiserfs-list@namesys.com
Subject: Re: mongo.pl PHASE_* options question
Date: Fri, 23 Jul 2004 02:25:59 +0400 [thread overview]
Message-ID: <41003EF7.6000003@namesys.com> (raw)
In-Reply-To: <20040722203115.2922715E03@mail03.powweb.com>
Hello,
unfortunately this is the very old mongo version. Please try the new one :
http://www.namesys.com/benchmarks/mongo-2003.06.24.tar.gz
which has an ability to selectively turn phases on/off.
The new options documentation will be added tomorrow.
Thanks,
Lena.
David Dabbs wrote:
>I’d like to reproduce the mongo tests as shown at
>
> http://www.namesys.com/benchmarks/v4marks.html
>
>The page presents the mongo options used to generate the results, but not
>all of these are documented at
>
> http://www.namesys.com/benchmarks/mongo_readme.html
>
>,and they are not mentioned in the mongo distribution README.
>
>
>FSTYPE= ext3 | reiserfs | reiser4
>MKFS= mkfs.<FSTYPE>
>
>DEV=/dev/hda2 (or whatever disk device)
>DIR=/mnt/testfs (mountpoint you must create)
>FILE_SIZE=4000
>BYTES=512000000
>#
># To have results free from buffer cache influence,
># settings must satisfy
>#
># BYTES * REP_COUNTER > ramsize
>#
>
>MOUNT_OPTIONS=<fs-specific mount options passed to MKFS command>
>
>NPROC=1
>REP_COUNTER=1
>SYNC=off
>WRITE_BUFFER=131072
>GAMMA=0.2
>
>DD_MBCOUNT=768
>
>#
># these are not documented
>#
>PHASE_COPY=cp
>PHASE_OVERWRITE=off
>PHASE_APPEND=off
>PHASE_READ=find
>PHASE_DELETE=rm
>PHASE_MODIFY=off
>
>
>A quick scan of mongo.pl code that validates options shows that the PHASE_*
>options are not present, so it is safe to assume that the PHASE* options are
>defunct. If this is the case, perhaps these options should be removed from
>the page.
>
>David
>
>
># description of all valid options which can be in an input file is a
># hash array each element of it has the following form:
># "key" => ["default value", flags, comment string]
>
>%OPTIONS = (
>"FSTYPE" => [ undef, $SHOULD_BE_SET, "filesystem type"],
>"DIR" => [ undef, $SHOULD_BE_SET, "fs mount point"],
>"MKFS" => [ undef, 0, "mkfs command"],
>"DEV" => [ undef, $SHOULD_BE_SET, "device file name"],
>"JOURNAL_DEV" => [ undef, 0, "journal device file name"],
>"JOURNAL_SIZE" => [ undef, 0, "journal size in 4K blocks"],
>"MOUNT_OPTIONS" => [ undef, 0, "mount options"],
>"BYTES" => [ undef, $SHOULD_BE_SET, "file set size (in bytes) created by all
>instances of reiser_fract_tree in one pass, "],
>"FILE_SIZE" => [ undef, $SHOULD_BE_SET, "median file size (a
>reiser_fract_tree parameter)"],
>"REP_COUNTER" => [3, 0, "number of passes for each mongo phase"],
>"NPROC" => [3, 0, "munber of processes running simultaneously"],
>"WRITE_BUFFER" => [4096, 0, "read/write buffer size parameter for mongo
>utilities"],
>"GAMMA" => ["0.0", 0, "the exponent of core distribution in
>reiser_fract_tree"],
>"SYNC" => [off, 0, "using O_SYNC/fsync options to iozone"],
>"DD_MBCOUNT" => [undef, 0, "size of largefile in megabytes"]
>
>
>
>
>
>
>
>
>
next prev parent reply other threads:[~2004-07-22 22:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 20:28 mongo.pl PHASE_* options question David Dabbs
2004-07-22 22:25 ` E. Gryaznova [this message]
[not found] <200407230209.14388.edward@namesys.com>
2004-07-22 22:20 ` David Dabbs
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=41003EF7.6000003@namesys.com \
--to=grev@namesys.com \
--cc=david@dabbs.net \
--cc=reiserfs-list@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.