| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Erik Rijkers <er(at)xs4all(dot)nl> |
| Cc: | alvherre(at)2ndquadrant(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Minmax indexes (timings) |
| Date: | 2013-11-15 16:28:57 |
| Message-ID: | 20131115162857.GE5489@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2013-11-15 17:11:46 +0100, Erik Rijkers wrote:
> I've been messing with minmax indexes some more so here are some results of that.
>
> Perhaps someone finds these timings useful.
>
>
> Centos 5.7, 32 GB memory, 2 quadcores.
>
> '--prefix=/var/data1/pg_stuff/pg_installations/pgsql.minmax' '--with-pgport=6444' '--enable-depend' '--enable-cassert'
> '--enable-debug' '--with-perl' '--with-openssl' '--with-libxml' '--enable-dtrace'
Just some general advice: doing timings with --enale-cassert isn't that
meaningful - it often can distort results significantly.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2013-11-15 16:33:56 | Re: Minmax indexes (timings) |
| Previous Message | Albe Laurenz | 2013-11-15 16:15:38 | Re: writable FDWs / update targets confusion |