From: | Feike Steenbergen <feikesteenbergen(at)gmail(dot)com> |
---|---|
To: | Gabriel Dodan <gabriel(dot)dodan(at)gmail(dot)com> |
Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: performance contradiction |
Date: | 2017-02-15 08:25:11 |
Message-ID: | CAK_s-G3sARA1-450K91HfHtMtZJRCzHPcGKtR9d_vDuAWyA8ag@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 23 January 2017 at 17:55, Gabriel Dodan <gabriel(dot)dodan(at)gmail(dot)com> wrote:
>
> BUT if I run a trivial select on both servers, on a similar table, the
select
> perform much much better on second server!
You're comparing two very different systems it seems, therefore you might be
looking at difference in the performance of EXPLAIN, just getting timing
information of your system may be the most expensive part[1], you could
disable
the timing explicity:
EXPLAIN (ANALYZE ON, TIMING OFF) <query>
And, there is something that stands out:
So it seems there is also some difference in the data, we could validate the
actual numbers:
SELECT sum(pg_column_size(symbols_tests))/count(*) FROM symbols_tests;
regards,
Feike
[1]
https://www.postgresql.org/docs/current/static/using-explain.html#USING-EXPLAIN-CAVEATS
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Beaton | 2017-02-17 07:59:10 | Correct use of cursors for very large result sets in Postgres |
Previous Message | PC Drew | 2017-02-09 18:48:16 | Inaccurate GiST Index Cost Causes DB Contention |