Re: [HACKERS] log_destination=file

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] log_destination=file
Date: 2017-11-30 04:44:17
Message-ID: CAB7nPqTU4zP=Qzr797ZVQrnSJbuQbRTKr7L=N-FLxJiXC5UKyA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 15, 2017 at 12:33 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Sun, Sep 10, 2017 at 5:29 AM, Dmitry Dolgov <9erthalion6(at)gmail(dot)com> wrote:
>> average latency:
>>
>> clients patch master
>> 10 0.321 0.286
>> 20 0.669 0.602
>> 30 1.016 0.942
>> 40 1.358 1.280
>> 50 1.727 1.637
>
> That's still a noticeable slowdown, though. And we've had previous
> reports of the overhead of logging being significant as well:
>
> http://postgr.es/m/CACLsApsA7U0GCFpojVQem6SGTEkv8vnwdBfhVi+dqO+gu5gdCA@mail.gmail.com
>
> I seem to recall a discussion, perhaps in-person, around the time Theo
> submitted that patch where it was reported that the logging collector
> could not be used on some systems he was working with because it
> became a major performance bottleneck. With each backend writing its
> own messages to a file, it was tolerable, but when you tried to funnel
> everything through a single process, the back-pressure slowed down the
> entire system unacceptably.

I have moved this patch to next CF for now.. The original patch still applies.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-11-30 04:45:35 Re: pl/perl extension fails on Windows
Previous Message Michael Paquier 2017-11-30 04:41:54 Re: pl/perl extension fails on Windows