Re: tuplestore potential performance problem

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: tuplestore potential performance problem
Date: 2009-01-15 15:36:29
Message-ID: 200901151536.n0FFaTQ27055@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hitoshi Harada wrote:
> 2009/1/15 Bruce Momjian <bruce(at)momjian(dot)us>:
> >
> > Has this been addressed?
>
> It is mentioned at
>
> http://archives.postgresql.org/pgsql-hackers/2008-12/msg01849.php
>
> * Look at tuplestore performance issues. The tuplestore_in_memory()
> thing is just a band-aid, we ought to try to solve it properly.
> tuplestore_advance seems like a weak spot as well.
>
> but not solved yet. It seems to me that to solve this the tuplestore's
> inside design should be changed much. In-file state doesn't use memory
> any more but it should be re-used for writing buffer, whereas the
> current desgin uses BufFile to do it, which causes tell/seek overhead
> for repeated put/get operation. And this is not for 8.4, I guess.

Oh, I see it is already on the TODO list; great. I have added
reference URL to the TODO.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2009-01-15 15:48:53 Re: Visibility map, partial vacuums
Previous Message Heikki Linnakangas 2009-01-15 15:23:46 Re: BUG #4566: pg_stop_backup() reports incorrect STOP WAL LOCATION