From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pgbench stats per script & other stuff |
Date: | 2016-03-20 06:39:16 |
Message-ID: | alpine.DEB.2.10.1603200725210.7678@sto |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-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(at)$f -b select-only(at)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
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2016-03-20 07:01:07 | Re: max_parallel_degree context level |
Previous Message | Andres Freund | 2016-03-20 04:14:09 | Re: Performance degradation in commit ac1d794 |