From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
To: Tomas Vondra <tv@fuzzy.cz>
Cc: Andres Freund <andres@2ndquadrant.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: 60 core performance with 9.3
Date: Thu, 31 Jul 2014 11:33:14 +1200
Message-ID: <53D980BA.1060800@catalyst.net.nz> (raw)
In-Reply-To: <3e6b532b0115ffff08e8d0debd76695b.squirrel@sq.gransy.com>
References: <53ACB190.2030206@catalyst.net.nz>
<CAOR=d=3=Y6yNtwQenwVBGe6ZgjAeA8PwgYb3=aQEKn+vYWhBJA@mail.gmail.com>
<53ACD6C4.9050605@catalyst.net.nz>
<20140627091951.GA16680@awork2.anarazel.de>
<53B283F3.7020005@catalyst.net.nz>
<20140701101307.GO21422@awork2.anarazel.de>
<53BF326F.2070903@catalyst.net.nz>
<20140711082207.GI17261@awork2.anarazel.de>
<53C711B6.5040802@catalyst.net.nz>
<53D84E16.90609@catalyst.net.nz>
<3e6b532b0115ffff08e8d0debd76695b.squirrel@sq.gransy.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
Hi Tomas,
Unfortunately I think you are mistaken - disabling the stats collector
(i.e. track_counts = off) means that autovacuum has no idea about
when/if it needs to start a worker (as it uses those counts to decide),
and hence you lose all automatic vacuum and analyze as a result.
With respect to comments like "it shouldn't make difference" etc etc,
well the profile suggests otherwise, and the change in tps numbers
support the observation.
regards
Mark
On 30/07/14 20:42, Tomas Vondra wrote:
> On 30 Červenec 2014, 3:44, Mark Kirkwood wrote:
>>
>> While these numbers look great in the middle range (12-96 clients), then
>> benefit looks to be tailing off as client numbers increase. Also running
>> with no stats (and hence no auto vacuum or analyze) is way too scary!
>
> I assume you've disabled statistics collector, which has nothing to do
> with vacuum or analyze.
>
> There are two kinds of statistics in PostgreSQL - data distribution
> statistics (which is collected by ANALYZE and stored in actual tables
> within the database) and runtime statistics (which is collected by the
> stats collector and stored in a file somewhere on the dist).
>
> By disabling statistics collector you loose runtime counters - number of
> sequential/index scans on a table, tuples read from a relation aetc. But
> it does not influence VACUUM or planning at all.
>
> Also, it's mostly async (send over UDP and you're done) and shouldn't make
> much difference unless you have large number of objects. There are ways to
> improve this (e.g. by placing the stat files into a tmpfs).
>
> Tomas
>
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mark.kirkwood@catalyst.net.nz, tv@fuzzy.cz, andres@2ndquadrant.com
Subject: Re: 60 core performance with 9.3
In-Reply-To: <53D980BA.1060800@catalyst.net.nz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox