From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Vlad <marchenko(at)gmail(dot)com> |
Cc: | PG-General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: 8.3RC2 vs 8.2.6 testing results |
Date: | 2008-01-28 22:35:07 |
Message-ID: | dcc563d10801281435i74d7a446ha90c7d7e360a5309@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Jan 28, 2008 3:56 PM, Vlad <marchenko(at)gmail(dot)com> wrote:
> Hello,
>
> 1. Freshly imported DB size on disk was about 3% smaller for 8.3
> 2. We ran several tests and found 8.3 generally 10% slower than 8.2.6.
> We took special measures to make sure that no third factors involved
> (no other apps running, all data was cached from disks, etc). Below
> is one of the queries that we used for testing (I anonymized table
> names) along with query plan for both 8.3 and 8.2. The query execution
> plans are the same for both versions, but what we found quite
> interesting is that if we add all the times from each line of 8.2's
> query plan, it roughly adds-up to the total execution time. For 8.3's
> plan each line shows a shorter time, yet resulting in longer total
> runtime. Also, summing 8.3's plan lines doesn't come close to the
> total execution time:
This last bit often means there's some overhead in the systems
timeofday() function calls.
If you just use \timing from psql, and run the script without explain
analyze, what speeds do you get on each?
From | Date | Subject | |
---|---|---|---|
Next Message | Vlad | 2008-01-28 22:41:22 | Re: 8.3RC2 vs 8.2.6 testing results |
Previous Message | Scott Marlowe | 2008-01-28 22:33:23 | Re: Table has duplicate keys, what did I do |