From: Nikita Danilov <Nikita@Clusterfs.COM>
To: Hans Reiser <reiser@namesys.com>
Cc: David Dabbs <david@dabbs.net>, reiserfs-list@namesys.com
Subject: Re: Unattended mongo benchmark?
Date: Sat, 31 Jul 2004 15:00:33 +0400 [thread overview]
Message-ID: <16651.31697.196453.840062@laputa.namesys.com> (raw)
In-Reply-To: <410B2BEA.6090508@namesys.com>
Hans Reiser writes:
> David Dabbs wrote:
>
> >I was wondering about a solution to running mongo benchmarks unattended.
> >If one does not exist, how about the following as a 'straw man' approach?
> >
> >Create a script (say mongo_auto.sh) that takes one numeric parameter. The
> >parameter would indicate which action/mongo script to perform next. The
> >parameters and their associated actions might be something like the
> >following:
> >
> >Parameter: N=0
> >- Make a copy of /etc/inittab
> >- Add a 'sysinit' entry in /etc/inittab that runs "/path/mongo_auto.sh 1"
> >- Reboot
> >
> >
> >Parameter: N
> >- Run the Nth mongo run (specified in a case statement in mongo_auto.sh)0.
> >- If (ran_without_error)
> > N = N + 1
> > if ( N <= Last_Run_Number)
> > - Update /etc/inittab entry to run "/path/mongo_auto.sh N"
> > - Reboot
> > else
> > - Clean up/restore /etc/inittab
> > - Run /path/to/mongo_parse.sh 1.log 2.log... > comparison.html
> >
> >
> >Or, to limit inittab mods to the start/end, the script could read/write a
> >.mongo_auto file that specifies the next run number to take.
> >
> >
> >David
> >
> >
> >
> >
> >
> >
> >
> sounds good.
Yes, Namesys has scripts to run arbitrary sequence of benchmarks with
reboots in between. These scripts plug themselves into
/etc/rc.d/boot.local rather than in /etc/inittab though.
>
Nikita.
next prev parent reply other threads:[~2004-07-31 11:00 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
[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 [this message]
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=16651.31697.196453.840062@laputa.namesys.com \
--to=nikita@clusterfs.com \
--cc=david@dabbs.net \
--cc=reiser@namesys.com \
--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.