Re: Performance options for CPU bound multi-SUM query

From: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
To: Matt <bsg075(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Performance options for CPU bound multi-SUM query
Date: 2016-01-28 05:37:15
Message-ID: CAKJS1f_yxkKPGrMWvzBhfs6EGWsDLXAevk3g9Lz72obRkUmkow@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 28 January 2016 at 08:41, Matt <bsg075(at)gmail(dot)com> wrote:
> Moving from NUMERIC to FLOAT(8) did indeed lower query times by about 20%.
>
> I will try fixeddecimal and agg() as time permits.

That's surprisingly little gain. Please note that you'll not gain any
further improvements from the fixeddecimal type than you won't have
already gotten from float8. My tests showed that it's very slightly
slower than float8, which is possibly due to float8 addition not
having overflow checks.

--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Kaushal Shriyan 2016-01-28 11:16:26 Difference between UDR and BDR replication
Previous Message Scott Mead 2016-01-28 04:58:10 Re: Catalog bloat (again)