Re: Vitesse DB call for testing

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Feng Tian <ftian(at)vitessedata(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Vitesse DB call for testing
Date: 2014-10-17 18:21:55
Message-ID: CAM3SWZQAGF5+Kb9W+u=L4ObLtwWQfDuPJ55X2oP9bORxMAGybQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 17, 2014 at 11:08 AM, Feng Tian <ftian(at)vitessedata(dot)com> wrote:
> I agree using that using int128 in stock postgres will speed up things too.
> On the other hand, that is only one part of the equation. For example, if
> you look at TPCH Q1, the int128 "cheating" does not kick in at all, but we
> are 8x faster.

I'm curious about how the numbers look when stock Postgres is built
with the same page size as your fork. You didn't mention whether or
not your Postgres numbers came from a standard build.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2014-10-17 18:25:00 Re: Vitesse DB call for testing
Previous Message Josh Berkus 2014-10-17 18:13:00 Re: Vitesse DB call for testing