Re: Optimizing prepared statements

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Jeroen T(dot) Vermeulen" <jtv(at)xs4all(dot)nl>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Optimizing prepared statements
Date: 2006-09-03 11:41:37
Message-ID: 87odtxw51q.fsf@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Jeroen T. Vermeulen" <jtv(at)xs4all(dot)nl> writes:

> For now, I'll summarize some results I got from randomized input data. I
> used very simple traces, with 11 prepared statements, each taking a
> different number of parameters (0 through 10, inclusive). All calls were
> uniformly randomized. I used LRU replacement of cached plans, with up to
> 4 retained plans per statement. Confidence counters ran from 0 to 3
> inclusive, with the confidence threshold lying between 1 and 2.

I'm confused, what exactly are you trying to predict? Whether each parameter
will be some cached value? Or whether the cached plan was correct?

> So once again, does anyone know of any realistic logs that I can use for
> more useful simulations?

You might look at the DBT test suite, iirc the TPCC spec it implements
intentionally mixes random queries with predictable queries.

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2006-09-03 13:37:41 Re: [HACKERS] [COMMITTERS] pgsql: Change FETCH/MOVE
Previous Message Michael Glaesemann 2006-09-03 11:00:30 Re: Interval month, week -> day