| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Rukh Meski <rukh(dot)meski(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgbench throttling latency limit |
| Date: | 2014-08-30 15:43:41 |
| Message-ID: | 20140830154341.GA25523@awork2.anarazel.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
I generally want to say that having a feature like this feels *very*
helpful to me. Lots of pg development hasn't really paid attention to
anything but the final pgbench results...
On 2014-08-29 19:48:43 +0200, Fabien COELHO wrote:
> + if (latency_limit)
> + printf("number of transactions above the %.1f ms latency limit: " INT64_FORMAT "\n",
> + latency_limit / 1000.0, latency_late);
> +
Any reason not to report a percentage here?
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2014-08-30 16:16:18 | Re: pgbench throttling latency limit |
| Previous Message | Kevin Grittner | 2014-08-30 14:46:31 | Re: delta relations in AFTER triggers |