| From: | Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com> |
| Cc: | pgsql-cluster-hackers(at)postgresql(dot)org |
| Subject: | Re: Function scan push-down using SQL/MED syntax |
| Date: | 2010-03-09 08:32:13 |
| Message-ID: | 20100309173213.99DD.52131E4D@oss.ntt.co.jp |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-cluster-hackers |
Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com> wrote:
> So, as the first step we implement it by tuplestore with the present
> libpq, but for further improvement we need to refactor or to extend
> our libpq to buffer some sized tuples. Or invent another
> more-data-fetching-oriented protocol like existing copy?
Before starting such optimization, we need some research for which
part is the performance bottleneck when sending large amount of data.
IMHO, since network is typically slower than in-memory data copy,
data compression and burst-transport would be more effective
even if they consume local CPU resources to convert the data format.
Regards,
---
Takahiro Itagaki
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2010-03-09 13:54:11 | Re: Function scan push-down using SQL/MED syntax |
| Previous Message | Hitoshi Harada | 2010-03-08 10:24:04 | Re: Function scan push-down using SQL/MED syntax |