Re: [PATCH] pgbench --throttle (submission 7 - with lag measurement)
В списке pgsql-hackers по дате отправления:
| От | Fabien COELHO |
|---|---|
| Тема | Re: [PATCH] pgbench --throttle (submission 7 - with lag measurement) |
| Дата | |
| Msg-id | alpine.DEB.2.02.1307171059050.3991@localhost6.localdomain6 обсуждение исходный текст |
| Ответ на | Re: [PATCH] pgbench --throttle (submission 7 - with lag measurement) (Greg Smith <greg@2ndQuadrant.com>) |
| Ответы |
Re: [PATCH] pgbench --throttle (submission 7 - with lag
measurement)
|
| Список | pgsql-hackers |
> The whole concept of "lag" with the rate limit is complicated. I must agree on that point, their interpretation is subtle. > At one point I thought this should be a debugging detail, rather than > exposing the user to it. The problem is that if you do that, you might > not notice that your limit failed to work as expected. Maybe it's good > enough in a case like this that the user will see they tried to limit at > 10000, but they only got 7135, so something must not have worked as > expected. Yep. As I suggested in answering to Tatsuo, the process can catch up later, so you could have 10000 in the end even with something amiss. -- Fabien.
В списке pgsql-hackers по дате отправления:
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера