| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
| Cc: | curtis(at)galtair(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Prepare enabled pgbench |
| Date: | 2002-11-13 02:42:22 |
| Message-ID: | 200211130242.gAD2gM814326@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tatsuo Ishii wrote:
> > > But one of the purposes of pgbench is examining performance on
> > > different environments, doesn't it? I'm afraid hard coded
> > > PREPARE/EXECUTE makes it harder.
> >
> > I was just thinking that pgbench is for measuring code changes, not for
> > testing changes _in_ pgbench. Once we know the performance difference
> > for PERFORM, would we still keep the code in pgbench? Maybe to test
> > later, I guess.
>
> My concern is PREPARE/EXECUTE may NOT always improve the
> performance. I guess we have very few data to judge PREPARE/EXECUTE is
> good or not. Moreover PREPARE/EXECUTE might be improved in the
> future. If that happens, keeping that switch would help examining the
> effect, no?
It would. I was just concerned that having both in there would be a
maintenance headache and would perhaps double the amount of code and
make it complicated. Let see what the author does and we can decide
then.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2002-11-13 02:55:20 | Re: Prepare enabled pgbench |
| Previous Message | Tatsuo Ishii | 2002-11-13 02:32:35 | Re: Prepare enabled pgbench |