Re: Wait events monitoring future development

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: ik(at)postgresql-consulting(dot)com, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Wait events monitoring future development
Date: 2016-08-08 17:03:41
Message-ID: 20160808170341.GC16416@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Aug 8, 2016 at 04:43:40PM +0530, Amit Kapila wrote:
> > According to developers, overhead is small, but many people have doubts
> > that it can be much more significant for intensive workloads. Obviously, it
> > is not an easy task to test, because you need to put doubtfully
> > non-production ready code into mission-critical production for such tests.
> > As a result it will be clear if this design should be abandoned and we
> > need to think about less-invasive solutions or this design is acceptable.
> >
>
> I think here main objection was that gettimeofday can cause
> performance regression which can be taken care by using configurable
> knob. I am not aware if any other part of the design has been
> discussed in detail to conclude whether it has any obvious problem.

It seems asking users to run pg_test_timing before deploying to check
the overhead would be sufficient.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Vik Fearing 2016-08-08 17:04:04 Re: Surprising behaviour of \set AUTOCOMMIT ON
Previous Message Vik Fearing 2016-08-08 16:54:52 Re: No longer possible to query catalogs for index capabilities?