| 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:20:07 |
| Message-ID: | 200211130220.gAD2K7J11712@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tatsuo Ishii wrote:
> > > Thanks. I can commit it for 7.4. BTW, it would be nice if we could
> > > have a switch to turn on/off PREPARE/EXECUTE in pgbench so that we
> > > could see how PRPARE/EXECUTE could improve the performance...
> >
> > We could probably just run before-after patch tests to see the
> > performance change. I am afraid adding that switch into the code may
> > make it messy.
>
> 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.
--
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:32:35 | Re: Prepare enabled pgbench |
| Previous Message | Tatsuo Ishii | 2002-11-13 02:16:17 | Re: Prepare enabled pgbench |