From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Jeff Janes <jeff.janes@gmail.com>
Cc: PostgreSQL Developers <pgsql-hackers@postgresql.org>
Subject: Re: pgbench stats per script & other stuff
Date: Sun, 20 Mar 2016 07:39:16 +0100 (CET)
Message-ID: <alpine.DEB.2.10.1603200725210.7678@sto> (raw)
In-Reply-To: <CAMkU=1wJapNYRPsieqxWEkgsTiFZguqxmjwv+1YT_dD5+G2R+A@mail.gmail.com>
References: <alpine.DEB.2.10.1507171544450.26125@sto>
<CAMkU=1wJapNYRPsieqxWEkgsTiFZguqxmjwv+1YT_dD5+G2R+A@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
Hello Jeff,
> So I wanted to do something like:
>
> for f in `seq 0 5 100`; do
> pgbench -T 180 -c8 -j8 -b tpcb-like@$f -b select-only@100
> done;
>
> But, I'm not allowed to specify a weight of zero.
Indeed. I did not envision such a use case, but it is quite legitimate and
interesting! I would hope that the behavior would be a linear combination
of the raw performance of each script, but whether it is indeed the case
is not that sure.
> Would this be a welcome change?
Speaking for myself, I would be fine with such a change, provided:
- that it does work:-) I'm not sure what happens by the script selection
process, it should be checked carefully because it was not designed
with allowing a zero weight, and it may depend on its/their positions.
It may already work, but it really needs checking.
- I would suggest that a warning is shown when a weight is zero,
something like "warning, script #%d weight is zero, will be ignored".
- the documentation should be updated:-)
--
Fabien
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: coelho@cri.ensmp.fr, jeff.janes@gmail.com
Subject: Re: pgbench stats per script & other stuff
In-Reply-To: <alpine.DEB.2.10.1603200725210.7678@sto>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox