pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rob Sargent <robjsargent@gmail.com>
To: Kenneth Marshall <ktm@rice.edu>
Cc: pgsql-sql@postgresql.org
Subject: Re: Extrapolating performance expectation
Date: Mon, 18 May 2009 09:22:54 -0600
Message-ID: <5c4ddc540905180822v398cd4bgd4bbbeb9456e022b@mail.gmail.com> (raw)
In-Reply-To: <20090518124701.GP28923@it.is.rice.edu>
References: <5c4ddc540905172104t1a91b829tc2848798a31df886@mail.gmail.com>
	<20090518124701.GP28923@it.is.rice.edu>

On Mon, May 18, 2009 at 6:47 AM, Kenneth Marshall <ktm@rice.edu> wrote:

> On Sun, May 17, 2009 at 10:04:46PM -0600, Rob Sargent wrote:
> > Can one extrapolate future performance expectations for ever-growing
> tables
> > from a given (non-trivial) data set, and if so with what curve?
>  Corollary:
> > what would one expect a performance curve to approximate in terms of
> query
> > execution time v. number of data rows (hardware, load staying constant).
> >
> > I have user and group information on system usage.  I would like to be
> able
> > to do year-to-date counts per user given a single group id but in the
> data
> > for one business quarter the query is taking in between 10 and 60+
>  seconds
> > depending on both on the size of the group and the group's total usage.
> > Groups typically have 10-100 users and consume 20K - 80K records in a 9M
> > record data set.  Group id column is indexed, but it is not the primary
> > index.  (Sad note: two pseudo groups account for 50 percent of the total
> > records IIRC (and will never be used for the usage-by-group query below)
> >
> > This is a single table query:
> >
> > select user_id, element_type, count(*)
> > from dataset
> > where group_id = N
> > group by user_id, element_type
> > order by user_id, element_type
> >
> > Is this the sort of situation which might benefit from increasing the
> number
> > of histogram bins (alter table alter column statistics (N>10))?
> >
> > Any and all pointers appreciated,
>
> Rob,
>
> What about partitioning the table based on the group. Then you could
> put the two pseudo groups in their own separate child table.
>
> Cheers,
> Ken
>

Ken,

Interesting point.  I'm hoping the psuedo groups are on the verge of
extinction but will certainly investigate the possibility.

R.

view thread (2+ messages)

Message-ID: <5c4ddc540905180822v398cd4bgd4bbbeb9456e022b@mail.gmail.com>
Permalink:  ../5c4ddc540905180822v398cd4bgd4bbbeb9456e022b@mail.gmail.com/
Also on:    postgresql.org/message-id/5c4ddc540905180822v398cd4bgd4bbbeb9456e022b@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: robjsargent@gmail.com, ktm@rice.edu
  Subject: Re: Extrapolating performance expectation
  In-Reply-To: <5c4ddc540905180822v398cd4bgd4bbbeb9456e022b@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox