| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Deferring some AtStart* allocations? |
| Date: | 2014-10-09 21:02:02 |
| Message-ID: | CA+TgmoaAi92=RQsGebO4YHK8DbLwKwd0s_ijN9qQSUKZrV0+YA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Oct 9, 2014 at 3:53 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
>> OK, here's an attempt at a real patch for that. I haven't perf-tested this.
>
> Neato. With a really trivial SELECT:
>
> before:
> tps = 28150.794776 (excluding connections establishing)
> after:
> tps = 29978.767703 (excluding connections establishing)
>
> slightly more meaningful:
>
> before:
> tps = 21272.400039 (including connections establishing)
> after:
> tps = 22290.703482 (excluding connections establishing)
>
> So that's a noticeable win. Obviously it's going to be less for more
> complicated stuff, but still...
>
> I've not really looked at the patches though.
Yeah, not bad at all for the amount of work involved. Want to
disclose the actual queries?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2014-10-09 21:03:00 | Re: Autovacuum fails to keep visibility map up-to-date in mostly-insert-only-tables |
| Previous Message | Bruce Momjian | 2014-10-09 20:58:51 | Re: Autovacuum fails to keep visibility map up-to-date in mostly-insert-only-tables |