| From: | Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com> |
|---|---|
| To: | Marko Kreen <markokr(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgsql_fdw, FDW for PostgreSQL server |
| Date: | 2012-02-08 12:24:40 |
| Message-ID: | 4F326988.5060509@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
(2012/02/02 18:24), Marko Kreen wrote:
> I think you want this instead:
>
> https://commitfest.postgresql.org/action/patch_view?id=769
With modified version of pgsql_fdw which uses row processor to retrieve
result tuples, I found significant performance gain on simple read-only
pgbench, though scale factor was very small (-s 3). Executed command
was "pgbench -S -n -c 5 T 30".
Average tps (excluding connections establishing) of 3 times measurements
are:
pgsql_fdw with SQL-cursor : 622
pgsql_fdw with Row Processor : 1219 - 2.0x faster than SQL-cursor
w/o pgsql_fdw(direct access) : 7719 - 6.3x faster than Row Processor
Row processor was almost 2x faster than SQL-cursor! I'm looking forward
to this feature.
In addition to performance gain, of course memory usage was kept at very
low level. :)
Regards,
--
Shigeru Hanada
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2012-02-08 12:35:15 | Re: xlog location arithmetic |
| Previous Message | Christian Nicolaisen | 2012-02-08 12:17:50 | Re: patch : Allow toast tables to be moved to a different tablespace |