| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| 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 16:16:18 |
| Message-ID: | alpine.DEB.2.10.1408301747090.10195@sto |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> + 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?
Yes: I did not thought of it.
Here is a v7, with a percent. I also added a paragraph in the documenation
about how the latency is computed under throttling, and I tried to reorder
the reported stuff so that it is more logical.
--
Fabien.
| Attachment | Content-Type | Size |
|---|---|---|
| pgbench-limit-7.patch | text/x-diff | 16.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ali Akbar | 2014-08-30 16:43:38 | Re: [PATCH] empty xml values |
| Previous Message | Andres Freund | 2014-08-30 15:43:41 | Re: pgbench throttling latency limit |