| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql: Remove pgbench "progress" test pending solution of its timing is |
| Date: | 2017-09-23 18:04:31 |
| Message-ID: | 20170923180431.w6mfwpcra5el5j2a@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Hi,
On 2017-09-23 19:57:40 +0200, Fabien COELHO wrote:
> According to the trace, the host was so loaded that it could not do anything
> for over two seconds, so that the first output is "progress: 2.6", i.e. the
> 0 thread did not get any significant time for the first 2.6 seconds... of a
> 1 second test. Hmmm, not very kind.
>
> Somehow this cannot be helped: if the system does not give any execution
> time to some pgbench thread, the expected output cannot be there.
skink runs postgres under valgrind, so it's going to be slower.
> If the test must run even when postgres doesn't, it is a little bit hard as
> a starting assumption for a benchmarking tool:-(
I'm unsure what the point of this is. It's not like we discussing
removing pgbench, we're talking about an unreliable test.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-09-23 18:05:51 | Re: pgsql: Remove pgbench "progress" test pending solution of its timing is |
| Previous Message | Fabien COELHO | 2017-09-23 17:57:40 | Re: pgsql: Remove pgbench "progress" test pending solution of its timing is |